Skip to main content
HTTP 422 Unprocessable Content
The request was well-formed syntactically but semantically invalid.
4xx · Client error✗ not retryable — fix the request instead
In AI APIs specifically
Some providers use 422 instead of 400 for parameter validation failures — the error body carries the field-level details.
Fix checklist
- Read the validation errors in the response body.
- Check enum values and parameter ranges against the API reference.
Spec: RFC reference
Related status codes
400 Bad Request
The server cannot process the request due to a client error — malformed JSON, invalid parameters, or schema violations..
401 UnauthorizedAuthentication is missing or invalid for this request..
402 Payment RequiredThe request requires payment — billing is not set up or a balance is exhausted..
403 ForbiddenThe server understood the request but refuses to authorize it — valid credentials, insufficient permission..