Guides
Handling API Errors
Our API uses standard HTTP status codes to indicate the success or failure of a request. When an error occurs, the response will include an error code and message. Your integration should handle these gracefully, with retry logic where appropriate, and surface clear messages to users when action is required.
| Status Code | Message | How to Resolve |
|---|---|---|
| 400 | Bad Request | Check your request payload and parameters for missing or invalid fields. |
| 401 | Unauthorized | Ensure you are using the correct API key with -u "$API_KEY:". |
| 403 | Forbidden | Your API key does not have permission. Confirm access rights or contact support. |
| 404 | Not Found | Verify the endpoint URL and resource ID. |
| 409 | Conflict | The resource is in an invalid state (e.g., duplicate request). Retry if safe. |
| 422 | Unprocessable Entity | Input validation failed. Check field formats and required attributes. |
| 429 | Too Many Requests | You have exceeded the rate limit. Implement retries with exponential backoff. |
| 500 | Internal Server Error | Temporary server issue. Retry the request or contact support if persistent. |
| 503 | Service Unavailable | API is temporarily unavailable. Retry with backoff. |