Skip to main content
The API uses conventional HTTP status codes and returns a JSON body with an error message (and often a message field with more detail).

​
Status codes

​
Error shape

​
Handling errors

401 means the credential itself was rejected — check the header and the key. 403 means the credential is valid but not permitted for that action.
Common on idempotent create operations (e.g. creating a wallet that already exists for a customer + network). Treat it as “already done” and read the existing resource.
Retry with exponential backoff and jitter. Never retry a non-idempotent write without a stable reference/idempotency key.
Always key your business logic off the HTTP status code first, then the error string. Message wording may change; status codes are stable.