|API RANK| by Escape.tech
Benchmark and ranking of 5138+ public APIs by Escape.tech
arcus API Documentation (ranked 2378 of 5138)
https://escape-data-and-specs.s3.fr-par.scw.cloud/specs/StMBG_ooLivjCay8fnsqL_arcus_api_documentation_json.jsonGENERAL INFORMATION
Introduction
<div class="panel panel-danger">
<div class="panel-body">
<h4><strong>Important:</strong> We are currently working on implementing
our Authentication method within this dynamic documentation, so that the
'Try it out' buttons located on each endpoint work as expected. However,
they can still be useful to show the basic Curl structure of the
requests, to which you would need to manually add the proper
Authentication header in order to obtain a successful response.</h4>
</div>
</div>
Welcome to arcus! Here you’ll find detailed information for integrating with
our API endpoints. We’ve tried to make this documentation as user-friendly
and example-filled as possible, but if you have any questions, please
contact us.
Integration happens in six easy steps:
- Sign NDA
- Receive staging (sandbox) API keys
- Complete compliance approval
- Sign commercial contract
- Receive production API keys
- Get certified
...
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 359 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 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!