Common Error Codes & Meanings

This reference provides explanations for common HTTP status codes you may encounter when using the Chutes API.

Code / Error	Description
`200 OK`	Request succeeded. The operation completed normally and returned valid data.
`202 Accepted`	Request accepted for processing but not yet completed (used for async operations).
`400 Bad Request`	Generic invalid request syntax or parameters (malformed JSON or missing fields).
`401 Unauthorized`	Invalid or missing API key — check your credentials or token.
`403 Forbidden`	Access denied — API key doesn’t have permission to access the resource.
`404 Not Found`	Requested chute, model, or endpoint does not exist.
`409 Conflict`	Resource conflict — often due to duplicate names or invalid state changes.
`422 Unprocessable Entity`	Input failed validation (e.g., schema mismatch, missing required fields).
`429 Too Many Requests`	Rate limit exceeded — too many API calls in a short time window.
`500 Internal Server Error`	Unexpected server-side failure; usually indicates a Chutes infrastructure problem.
`502 Bad Gateway`	Server acting as a gateway received an invalid response from the model backend.
`503 Service Unavailable`	Chutes platform temporarily overloaded or under maintenance — retry later.
`504 Gateway Timeout`	Request took too long; backend did not respond in time.

Tip: If you encounter frequent 429 or 503 responses, implement retry logic with exponential backoff to avoid exceeding rate limits or overloading the system.