|API RANK| by Escape.tech
Benchmark and ranking of 5138+ public APIs by Escape.tech
Microsoft Bot Connector API - v3.0 (ranked 976 of 5138)
https://escape-data-and-specs.s3.fr-par.scw.cloud/specs/Microsoft_Bot_Connector_API_v3_0_9f0c3400_11da_4a82_9b21_11f936aeee60_json.jsonGENERAL INFORMATION
The Bot Connector REST API allows your bot to send and receive messages to channels configured in the
Bot Framework Developer Portal. The Connector service uses industry-standard REST
and JSON over HTTPS.
Client libraries for this REST API are available. See below for a list.
Many bots will use both the Bot Connector REST API and the associated Bot State REST API. The
Bot State REST API allows a bot to store and retrieve state associated with users and conversations.
Authentication for both the Bot Connector and Bot State REST APIs is accomplished with JWT Bearer tokens, and is
described in detail in the Connector Authentication document.
Client Libraries for the Bot Connector REST API
- Bot Builder for C#
- Bot Builder for Node.js
- Generate your own from the [Connector API Swagger file](https://raw.git
...
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 5/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 47.9 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!