422
Unprocessable Content
Client errors (4xx)·RFC 9110
What 422 means
The request was well-formed but contains semantic errors that prevent processing.
Widely used by APIs for validation failures — the syntax is valid JSON but a field fails business rules.
Client errors (4xx)
The request contains an error from the client — bad syntax, missing auth or a wrong URL.
Other 4xx codes
400Bad Request401Unauthorized402Payment Required403Forbidden404Not Found405Method Not Allowed406Not Acceptable407Proxy Authentication Required408Request Timeout409Conflict410Gone411Length Required412Precondition Failed413Content Too Large414URI Too Long415Unsupported Media Type416Range Not Satisfiable417Expectation Failed418I'm a teapot421Misdirected Request423Locked424Failed Dependency425Too Early426Upgrade Required428Precondition Required429Too Many Requests431Request Header Fields Too Large451Unavailable For Legal Reasons
FAQ — 422
What does HTTP 422 mean?
422 Unprocessable Content: The request was well-formed but contains semantic errors that prevent processing. Widely used by APIs for validation failures — the syntax is valid JSON but a field fails business rules.
Which class does status code 422 belong to?
422 is a Client errors (4xx) code. The request contains an error from the client — bad syntax, missing auth or a wrong URL.
Where is the 422 code defined?
Status code 422 is defined in RFC 9110 and is part of the IANA HTTP Status Code Registry.