Errors & Rate Limits
HTTP status codes
Section titled “HTTP status codes”All Presto APIs use standard HTTP status codes. Successful responses return 2xx; errors return the appropriate 4xx or 5xx code with a JSON body describing the problem.
| Status | Meaning |
|---|---|
| 200 OK | Request succeeded |
| 201 Created | Resource created successfully |
| 400 Bad Request | Invalid request body or missing required fields |
| 401 Unauthorized | Missing, invalid, expired, or revoked API key |
| 403 Forbidden | Valid key, but not authorized for the requested operation |
| 404 Not Found | Resource does not exist |
| 429 Too Many Requests | Rate limit exceeded — back off and retry |
| 500 Internal Server Error | Unexpected server error |
Rate limiting
Section titled “Rate limiting”The API enforces per-key rate limiting. Each API key has its own request budget, independent of other keys.
The default limit is 600 requests per hour per API key. Contact your organization administrator if you need a higher limit.
When you exceed the limit, the API returns 429 Too Many Requests. Back off and retry after a short delay.
Retry guidance
Section titled “Retry guidance”- 401/403: Do not retry — fix the authentication or authorization issue
- 429: Retry with exponential backoff
- 500: Retry with backoff; if persistent, contact support