Errors
Every Cashela API error answers success: false with a human-readable message. Validation errors (422) add errors, a map of each invalid field to its messages; domain errors may add a stable code.
{ "success": false, "message": "Unauthorized."}Common to every product
| HTTP | Message | What to do |
|---|---|---|
401 | Unauthorized. | Check the key and its status in the Developer Portal. Missing or wrong credentials, credentials of the other environment, or a disabled, revoked or expired key. |
403 | IP address is not allowed. | The key has an IP whitelist and the request came from another address. |
403 | Insufficient permissions. | The key may not use that endpoint. Contact support. |
422 | Field messages in errors | Fix the fields. Nothing was created. |
429 | — | Wait for the seconds in Retry-After, then retry with backoff. |
500 / 503 | — | Retry later. If it persists, contact support with your X-Trace-Id. |
By product
- Pay-In: full envelope, HTTP statuses and every error code in Pay-In errors.
- Pay-Out: see the Pay-Out guide.
Read code when it is present, but do not require it. Always log the X-Trace-Id you sent with the response.