|API RANK| by Escape.tech
Benchmark and ranking of 5138+ public APIs by Escape.tech
Beetexting Connect (ranked 3424 of 5138)
https://escape-data-and-specs.s3.fr-par.scw.cloud/specs/xonZqWgjvINofoqLwOWZO_beetexting_connect_json.jsonGENERAL INFORMATION
The Beetexting Connect API is organized around REST. Our API has predictable resource-oriented URLs, accepts form-encoded request bodies, returns JSON-encoded responses, and uses standard HTTP response codes, authentication, and verbs.<h1> Authentication </h1> <p>The Beetexting Connect API uses OAuth2.0 mechanism to authenticate requests. You can view and manage your client id and client secret in the Beetexting application. <p> Your credentials carry many privileges, so be sure to keep them secure! Do not share your credentials in publicly accessible areas such as GitHub, client-side code, and so forth. All API requests must be made over HTTPS, with an exception to localhost which can use HTTP. <h1>Beetexting Connect Accounts </h1> <p>Clients can create Beetexting Connect accounts using the application, which takes in the Client App Name, Callback URL's and provides Client Id and Client Secret. Thus, obtained Client Id and Client Secret are used to make requests to the API.
Contact
- Name: buzz@beetexting.com
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: A05:2021
PERFORMANCE 3/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 353 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 1/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 3.0.1 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!