|API RANK| by Escape.tech
Benchmark and ranking of 5138+ public APIs by Escape.tech
Viper API Documentation (ranked 3086 of 5138)
https://escape-data-and-specs.s3.fr-par.scw.cloud/specs/t_hsGtBsHysEUaCqeQIRg_viper_api_documentation_json.jsonGENERAL INFORMATION
Integration Definition
This document defines the activities necessary to integrate the software units and software components into the software item. The integration document contains an overview of VIPER API, a brief description of the major task involved in the integration, the overall resources needed to supports the integration effort. The plan is developed during the Development Phase and is updated during the Integration and Test Phases; the final version is provided in the Implementation Phase.
<hr>
Audience
The intended audience of this document is the Operator who is in-charge for the integration process. All personnel responsible for the integration, implementation should read and understand this document.
This document provides guidance to the developers in helping them for the construction of code and storage mechanism for related data.
The Operator can verify the design and see if all of the functionality is covered to perform the full integration.
...
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 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 229 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!