|API RANK| by Escape.tech
Benchmark and ranking of 5138+ public APIs by Escape.tech
Parcelow API (ranked 1942 of 5138)
https://escape-data-and-specs.s3.fr-par.scw.cloud/specs/T7ZYt7stdX_ShPUN5FFSg_parcelow_api_json.jsonGENERAL INFORMATION
The purpose of this documentation is to guide the developer on how to integrate with the Parcelow Payment API, by describing its functionality, the methods to be used, by listing information to be sent and received, and providing examples.<br> The integration mechanism with the Payment API is simple, so only intermediate knowledge of Web programming language, HTTP/HTTPS requests, and JSON file manipulation are required to successfully deploy the solution.<br> In this manual you will find references on all the operations available for the Payment REST API. These operations must be performed using your specific key (Client ID and Client Secret) on the respective endpoints of the environments. <br><br> Register Access Client <br> To have access to the API, you must first request the registration of your client via e-mail. <br> The system you are integrating must have an account already active on the Parcelow system. <br> When requesting the client's registration, it is necessary t
...
Contact
- Name: you@your-company.com
SECURITY 3/5
The security score of an API is computed as the number of OWASP top 10 vulnerabilities detected in the API.
- OWASP issues detected: API5:2023, API7:2023
PERFORMANCE 4/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 149 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!