|API RANK| by Escape.tech
Benchmark and ranking of 5138+ public APIs by Escape.tech
Adyen Checkout API (ranked 33 of 5138)
https://escape-data-and-specs.s3.fr-par.scw.cloud/specs/Adyen_Checkout_API_ea21f48f_f85b_46a1_b75b_9883286eff4f_json.jsonGENERAL INFORMATION
Adyen Checkout API provides a simple and flexible way to initiate and authorise online payments. You can use the same integration for payments made with cards (including 3D Secure), mobile wallets, and local payment methods (for example, iDEAL and Sofort).
This API reference provides information on available endpoints and how to interact with them. To learn more about the API, visit Checkout documentation.
Authentication
Each request to the Checkout API must be signed with an API key. For this, obtain an API Key from your Customer Area, as described in How to get the API key. Then set this key to the X-API-Key
header value, for example:
curl
-H "Content-Type: application/json" \
-H "X-API-Key: Your_Checkout_API_key" \
...
Note that when going live, you need to generate a new API Key to access the [live endpoints](https://docs.adyen.com/development-r
...
Contact
- Name: Adyen Developer Experience team
- Name: developer-experience@adyen.com
- Contact API maintainers
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 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 68.2 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.1.0 schema specification.
- Contains comments and summaries.
- Contains examples.
- Does not contain duplicated objects.
Popularity 3/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!