API errors
HTTP status codes and error handling for the Platform API.
1 min read
The Platform API uses standard HTTP status codes to communicate request outcomes.
| Status code | Name | Description |
|---|---|---|
| 200 | OK | The request succeeded. |
| 201 | Created | The resource was created. |
| 400 | Bad Request | The request could not be processed. Check the request format and parameters. |
| 401 | Unauthorized | Authentication failed. Verify your X-Auth-Token header. |
| 403 | Forbidden | You do not have permission to access this resource. |
| 404 | Not Found | The requested resource does not exist. |
| 409 | Conflict | The request conflicts with the current state of the resource. |
| 422 | Unprocessable Entity | The request was well-formed but contains semantic errors. |
| 429 | Too Many Requests | The rate limit has been exceeded. See rate limiting. |
| 500 | Internal Server Error | An unexpected error occurred. Retry after a short delay. |
| 503 | Service Unavailable | The service is temporarily unavailable. Retry after a short delay. |
For 5xx errors and transient failures such as 408 (Request Timeout) and 429 (Too Many Requests), implement retries with exponential backoff. See rate limiting for guidelines.
How is this guide?