Error Responses
Our API uses standard HTTP status codes to indicate success or failure. All error responses return a structured JSON body that includes acode, message, and optionally, details.
Common HTTP Status Codes
| Code | Meaning | Description |
|---|---|---|
| 200 | OK | Request was successful. |
| 201 | Created | Resource was successfully created. |
| 400 | Bad Request | The request is invalid (e.g., missing fields, invalid format). |
| 401 | Unauthorized | Invalid or missing API key. |
| 403 | Forbidden | Authenticated, but not allowed to perform the operation. |
| 404 | Not Found | Resource not found or endpoint incorrect. |
| 409 | Conflict | Duplicate resource creation or logic conflict (e.g., reused idempotency key). |
| 429 | Too Many Requests | Rate limit exceeded. |
| 500 | Internal Server Error | An unexpected server-side error occurred. |
| 503 | Service Unavailable | Temporary downtime or overload. Try again later. |
Sample Error Response
Debugging Tips
- Check the
codeandmessagefields for immediate clarity on the error. - Use the
request_idwhen contacting support to help trace the exact call. - Ensure your
Content-Typeis set toapplication/jsonand all required fields are included.
Handling Rate Limits
If you receive a429 Too Many Requests, inspect the following response headers:
| Header | Description |
|---|---|
X-RateLimit-Limit | Max requests per minute allowed |
X-RateLimit-Remaining | Number of remaining requests in current window |
X-RateLimit-Reset | Time (Unix epoch) when the limit resets |
Retrying Safely
For paid endpoints, we recommend using Idempotency Keys to prevent duplicate billing during retries.Still Stuck?
If an error persists, contact us at support@antei.com and include:- The
request_idfrom the response - Your API key type (
liveorsandbox) - A short description of what you were trying to do