What Is the 422 Status Code? (Unprocessable Entity)
On this page
HTTP 422 Unprocessable Entity means the request was well-formed but failed validation. The syntax is fine but the server can't process the contents — usually a validation failure on the payload (a missing field, a wrong type, a value that breaks a business rule). It's also written “HTTP 422” or just “422 error” / “422 status code.”
Quick facts
| Status code | 422 |
|---|---|
| Meaning | Unprocessable Entity |
| Category | 4xx Client Error |
| Common causes (scraping) | Missing required field, wrong type, value out of allowed range |
| Right response | Fix the request / retry with backoff; for disguised blocks use a real-browser unblock |
Related terms
Concept map
How 422 Status Code (422 Unprocessable Entity) connects
The terms most directly tied to this one. Hover a node to see its neighbours, click to preview, drag to rearrange.
Tools & solutions for this topic
Frequently asked questions
Is 422 a client or server error?
It's a client-side (4xx) error — the server is pointing at something in your request.
Does a 422 mean I'm blocked when scraping?
Not necessarily. 422 points at your request, not a ban — but anti-bot layers sometimes return it instead of a 403, so check the response body and headers.
How do I fix a 422 error?
The request was well-formed but failed validation is the cause, so the fix targets that. Correct the offending part of the request, then retry.
What's the difference between 422 and 400?
400 Bad Request usually means the server couldn't parse the request at all (malformed syntax). 422 means it parsed fine but the values failed validation. 400 = can't read it, 422 = read it, didn't like it.
Last updated: 2026-05-28