Developers
Checkout, digital delivery and store APIs.
Limits & errors
When a request returns HTTP 429, respect the Retry-After header when present. Otherwise use exponential backoff with jitter. Avoid retrying invalid requests or authentication failures unchanged.
Limits depend on the endpoint and deployment configuration. Do not assume a fixed per-key allowance or rely on rate-limit headers being present on every response.
| Status | Next step |
|---|---|
400 | Check the JSON body, required fields and product identifiers. |
401 / 403 | Check the store API key, its scopes and store access. |
404 | Check the store slug and resource identifier. |
405 | Use the HTTP method listed for the endpoint. |
429 | Wait before retrying; reduce request concurrency. |
5xx | Retry safe reads with backoff. Check the order before retrying a purchase. |
For endpoints that support idempotency, reuse the same idempotency key for retries of the same operation. Never create a new key just because a payment request timed out.