Errors
Every error response shares a common shape, including a requestId you should log and reference when contacting support.
Error object shape
json
{
"ok": false,
"statusCode": 400,
"message": "amountMinor must be a positive integer string",
"requestId": "req_9f3a2b1c",
"timestamp": "2026-07-08T15:04:12.331Z"
}HTTP status codes
| Status | Meaning | How to fix |
|---|---|---|
| 400 | Bad request | Check the response body's message field — usually a validation error on one field. |
| 401 | Unauthorized | Your API key is missing, invalid, or revoked. Confirm you're using the right key for the target environment. |
| 403 | Forbidden | The key is valid but not authorized for this resource — e.g. a sandbox key against production data. |
| 404 | Not found | The resource ID doesn't exist, or belongs to a different company — the API never leaks existence across accounts. |
| 409 | Conflict | The action conflicts with the resource's current state, e.g. refunding an already-fully-refunded payment. |
| 429 | Too many requests | You've exceeded a rate limit. Respect the Retry-After header and back off. |
| 500 | Internal error | Something failed on our side. Retry with backoff; if it persists, contact support with the requestId. |
Was this page helpful?