Adyen Checkout API OpenAPI spec score

Octri scored the public spec at https://raw.githubusercontent.com/Adyen/adyen-openapi/main/json/CheckoutService-v71.json for what a code generator can do with it. This is a reading of the document, not a grade of the API.

8.7/ 10
Strong

28 operations · 264 models · 7 tags · OpenAPI 3.1.0

Scored 29 October 2026 · fingerprint cc68947b5ef6… · spec version 71 · server checkout-test.adyen.com

Document last changed 29 October 2026.

Where the points went

Every rule, heaviest first, with what it cost this document, how much of the surface it touched, and where. The rule id links to what that rule checks.

RuleWeightResultSurfaceLocations
Successful responses declare a schemaresponse-schema2.0Clean28 operations cleanNothing found
Shared models live in components and are $ref'dshared-schemas-referenced2.0Clean28 operations cleanNothing found
Generated public names do not collideoperation-id-unique2.0Clean28 operations cleanNothing found
Every path placeholder has a parameterpath-parameters-declared1.5Clean28 operations cleanNothing found
Every operation declares an operationIdoperation-id-present1.0Clean28 operations cleanNothing found
operationIds read as method namesoperation-id-naming1.0Clean28 operations cleanNothing found
Operations carry a summary or descriptionoperation-documented1.0Clean28 operations cleanNothing found
Request bodies are documentedrequest-body-documented1.00.9 lost24 of 28 operationsPOST /originKeysPOST /paypal/updateOrderPOST /validateShopperIdand 21 more
Failure responses are declarederror-responses1.00.4 lost8 of 28 operationsPOST /applePay/sessionsPOST /cardDetailsGET /sessions/{sessionId}and 5 more
Operations are taggedoperation-tagged1.0Clean28 operations cleanNothing found
No duplicate or equivalent pathsduplicate-paths1.0Clean26 paths cleanNothing found
Authentication is describedsecurity-declared1.0CleanDeclaredNothing found
Parameters explain their purposeparameters-documented0.75Clean28 operations cleanNothing found
A server URL is declaredserver-url0.5CleanDeclaredNothing found

What 8.7 means for an SDK

A strong reading, and the three rules that decide most of it.

A generator has what it needs here: typed methods, named models and doc comments that say something. What is left is polish, and it can wait until after the first release.

Three rules carry six of the 10 points between them. On this document they took 0.0.

Clean

Successful responses declare a schema

28 operations clean

Clean

Shared models live in components and are $ref'd

28 operations clean

Clean

Generated public names do not collide

28 operations clean

What to change first

Every rule that deducted, in the order they cost.

  1. 0.9 lost

    Request bodies are documented

    Describe the body, or the fields inside it. Field-level prose is the one that reaches the SDK's arguments.

    Inside Octri this one has a one-click fix.

  2. 0.4 lost

    Failure responses are declared

    Declare the failures you actually return, or one `default` response carrying your error shape.

The spec at raw.githubusercontent.com is public. Octri keeps the `info` block, the score, and up to five sample finding locations per rule. The document itself is not stored and is not served from here. The audit predicts what an SDK generator can do with the description; it is not a security review, an uptime measurement or a critique of the API’s design. This page is not affiliated with Adyen Checkout API or Adyen Developer Experience team.