|API RANK| by Escape.tech
Benchmark and ranking of 5138+ public APIs by Escape.tech
Bot Connector - Direct Line API - v3.0 (ranked 4040 of 5138)
https://escape-data-and-specs.s3.fr-par.scw.cloud/specs/w8uX3D21Z9OG8bZjt7_i7_bot_connector___direct_line_api___v3_0_json.jsonGENERAL INFORMATION
Direct Line 3.0
The Direct Line API is a simple REST API for connecting directly to a single bot. This API is intended for developers
writing their own client applications, web chat controls, mobile apps, or service-to-service applications that will
talk to their bot.
Within the Direct Line API, you will find:
- An authentication mechanism using standard secret/token patterns
- The ability to send messages from your client to your bot via an HTTP POST message
- The ability to receive messages by WebSocket stream, if you choose
- The ability to receive messages by polling HTTP GET, if you choose
- A stable schema, even if your bot changes its protocol version
Direct Line 1.1 and 3.0 are both available and supported. This document describes Direct Line 3.0. For information
on Direct Line 1.1, visit the Direct Line 1.1 reference documentation.
Authentication: Secrets and Tokens
Direct L
...
Contact
- Name: Bot Framework
- Name: botframework@microsoft.com
- Contact API maintainers
License
- Name: The MIT License (MIT)
- See License
SECURITY 4/5
The security score of an API is computed as the number of OWASP top 10 vulnerabilities detected in the API.
- OWASP issues detected: API7:2023
PERFORMANCE 1/5
The performance score is derived from the median response time of the API, sometimes referred as p50. The median is the value separating the higher half from the lower half of a data sample, here the response times of the API.
- The median response time of the API is 1,040 ms .
Get p50 under 220 ms to get a 4/5 score.
RELIABILITY 5/5
The reliability score is derived from the number of inconsistent server responses, either server errors or non-conforming return values.
- Self compliance: response objects matched the declared response types.
- Server errors: the server did not return any 5xx error.
DESIGN 2/5
The design score reflects the quality of the specification file (usually named openapi.json or swagger.json). Having a high-quality specification file (with up-to-date types and examples) help developers understand the API and tools produce relevant documentation.
- Respects OpenAPI 2.0 schema specification.
- Contains comments and summaries.
- Contains examples.
- Does not contain duplicated objects.
Popularity 0/5
The popularity score is computed from the number of references to the API found on the internet. Have your API used by many developers to get a higher score!