Skip to content
4xx · Client Error

422 Unprocessable Content

The request was well-formed but contains semantic errors that prevent processing.

What it means

HTTP 422 Unprocessable Content (originally Unprocessable Entity) means the server understood the request and its syntax was fine, but the content fails validation. Unlike 400, where the request itself is malformed, here the request parses correctly and is simply asking for something the data does not allow — a required field missing, a value out of range, a rule violated.

When it happens

It happens with API validation failures: submitting a form or JSON payload that parses fine but breaks a business rule, such as an email already in use or a date in the past where a future date is required.

How to fix it

  • Read the validation errors in the response body and correct the offending fields.
  • Make sure values meet the API's rules — required fields present, formats and ranges valid.
  • For your own API, return clear, field-level error messages so clients know what to fix.

SEO impact

None directly. It is a validation response for API submissions and does not apply to indexable pages.

Check it with Sitewell

Find out which of your URLs return 422

Paste a list of URLs and Sitewell checks the status code of every one at once — free and without signup.

Related codes

Related guides