422
Unprocessable Entity
4xx · Client Error
The request was well-formed but had semantic errors (often validation).
What does HTTP 422 Unprocessable Entity mean?
The server understands the content type and the syntax is correct, but it cannot process the contained instructions — typically because of validation errors. It is common in REST and form APIs.
4xx responses indicate the request was faulty: bad syntax, missing authentication, or a resource that does not exist. The fix usually lives on the client/request side.
Common causes
- Validation failures (e.g. invalid email, value out of range)
- Business-rule violations in an otherwise valid payload
How to fix a 422 error
- Surface field-level validation errors to the user
- Correct the data to satisfy the API’s rules
- Check the response body for details on which fields failed
Related 4xx status codes
Look up and search every HTTP status code in one place.
Open the HTTP Status Code tool