|API RANK| by Escape.tech
Benchmark and ranking of 5138+ public APIs by Escape.tech
CarChip Connect API (ranked 3882 of 5138)
https://escape-data-and-specs.s3.fr-par.scw.cloud/specs/de97gCFBaUi4FPKQ9cTld_carchip_connect_api_json.jsonGENERAL INFORMATION
The CarChip Connect API is a REST style API that returns JSON data about your organization's Locations, Fleets, Vechiles, and Drivers.
Ignore the error messages at the top of this documentation page about partial path templating. The URL paths defined in this documentation are correct and do work.
In the CarChip Connect system the Vehicles are organized under Companies. When you call the API you can only interact with one Company at a time. This is for security reasons.
The CarChip Connect API uses an API Key and API Signature technique to sign each request to prevent others from accessing your data. As a developer using the CarChip Connect API you will be given an API Key and an API Secret. You need to keep the API Secret protected because it is used to sign your requests to the API. When you build an application for the CarChip API you will need a different API Key and API Secret for each Company in the CarChip Connect system that you interact with. This is for security reason
...
SECURITY 5/5
The security score of an API is computed as the number of OWASP top 10 vulnerabilities detected in the API.
- OWASP: We didn't find any OWASP vulnerability.
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 5,000 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!