|API RANK| by Escape.tech
Benchmark and ranking of 5138+ public APIs by Escape.tech
Changing Health Public API (ranked 5106 of 5138)
https://escape-data-and-specs.s3.fr-par.scw.cloud/specs/dtw6vw6x9Rmpst1EJa0G9_changing_health_public_api_json.jsonGENERAL INFORMATION
Specification for Changing Health Public API
Changing health API problem template
Please fill out the template below, it will allow us to better understand issues you’re experiencing with the API and assist properly.
FAQe
Please check the following before sending the error report:
-
If you receive a 401 code in the response, please make sure that you’ve added "Authorization" header to the request with the correct token you received.
-
When you get the code 422 in the response with information about the incorrect
unit_id
orpackage_id
, please make sure that the value you provide in the body request matches the one you received from Changing Health. -
Each response containing status code
422
relates to validation errors. Before submitting your application, make sure your request body complies with the guidelines contained in the documentation.
Issue Template:
Request URL:
Request Method:
Request Headers[please make sure you add
...
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 0/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 4,800 ms .
Get p50 under 220 ms to get a 4/5 score.
RELIABILITY 0/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 returned 5xx errors.
DESIGN 3/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!