|API RANK| by Escape.tech
Benchmark and ranking of 5138+ public APIs by Escape.tech
StatusHub API v1 (ranked 4599 of 5138)
https://escape-data-and-specs.s3.fr-par.scw.cloud/specs/4zdwuZa42Sk39xLd4u_zV_statushub_api_v1_json.jsonGENERAL INFORMATION
Deprecation warning
This API version is deprecated and API V2 should be used instead
Authentication
Authentication is performed with API Key. To generate API Key please sign in to StatusHub, go to tab "Account" and then choose "API Key" from menu. API Key should be passed as a part of a query string with name api_key.
Rate limiting
StatusHub API has two rate limits:
- GET requests - 30 requests per second
- All other requests - 5 requests per second
Rate limit is bounded to API Key used for authentication
When rate limit will be exceeded, StatusHub API will respond with:
- 429 response code
{"error":"Too many requests - please retry later"}response- Retry-After response header
In special cases certain API method may have different rate limit which will be mentioned in API method description
Time zones
All date/time parameters should be passed in UTC zone no matter the default zone Hub settings
Contact
- Name: pawel@statushub.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 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 969 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.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!