|API RANK| by Escape.tech
Benchmark and ranking of 5138+ public APIs by Escape.tech
Bayonet Payments API (ranked 684 of 5138)
https://escape-data-and-specs.s3.fr-par.scw.cloud/specs/FzJUAatbj2dNkNzJ2Ecuf_bayonet_payments_api_json.jsonGENERAL INFORMATION
Bayonet Payments API is a Payments Orchestration Layer service allowing customers to integrate several Gateway services through a single API.
Quickstart Postman Collection
Get our Payments API Quickstart Postman collection to start testing our API right away.
Scheme
All API requests must use https [TLS >= 1.2]. Plain http requests will be rejected.
Authentication
Authentication is required for all of the endpoints present in this documentation. Authentication is performed via bearer auth. You must provide your API key as the bearer token in the headers, eg. Authorization: Bearer <API KEY>. A 401 Unauthorized or a 403 Forbidden response is generally returned in case of invalid API key or invalid permissions.
Errors
We use conventional HTTP response codes to communicate success or error. 2xx response codes are retur
...
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 2/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 597 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 4/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!