Skip to main content
When an error occurs, the Venice API returns an HTTP status code and a descriptive message. Some errors also include additional fields, such as refund status, suggested retry models, validation details, or request IDs.

Error response format

Most errors return an error field with a human-readable message:
Some endpoints include additional fields that are specific to the endpoint. For example, video moderation errors can include whether credits were refunded:
Validation errors may include details and issues fields with field-level validation information:
Some OpenAI-compatible endpoints may return OpenAI-style error objects for specific cases, such as context length errors:

Missing credentials

A request with no credentials returns 402 Payment Required, not 401. Every paid route also accepts x402 wallet authentication, so the response is a payment challenge: it includes a PAYMENT-REQUIRED header and a body describing both ways to authenticate.
If you meant to use an API key, check that the Authorization: Bearer header is set. A key that is present but invalid returns 401.

Request format errors

These errors come from reading the request body, before any endpoint-specific validation runs. A wrong Content-Type returns 400, not 415. Size-limit 413 responses also include a code field:

Error codes

Other errors

The table above is not exhaustive. Some errors are returned without a listed code, and messages can vary by model and endpoint, so branch on the HTTP status rather than on message text. Errors you may see that aren’t in the table: