HTTP 422 Unprocessable Content

The request is well formed, but the data in it doesn’t make sense, such as failing validation.

Unprocessable Content

4xx Client errorStandardRFC 9110, section 15.5.21

The request is well formed, but the data in it doesn’t make sense, such as failing validation.

Example response
HTTP/1.1 422 Unprocessable Content
Content-Type: application/problem+json
Date: Sun, 15 Nov 2026 09:30:00 GMT

{"title":"Validation failed","errors":[{"field":"email","message":"is not a valid email address"}]}

What 422 means

The server understands the format and the syntax is fine, but it can’t process the data in it. In practice: validation failed. It was called “Unprocessable Entity” in WebDAV and was renamed “Unprocessable Content” when RFC 9110 made it part of core HTTP.

When servers send it

In APIs, when a field is missing, has the wrong type, is out of range, or breaks a business rule. Rails, Laravel, FastAPI and others use it for validation errors by default.

Common causes

  • A required field missing or empty.
  • A value in the wrong format, such as an invalid email or a date like 2026-02-30.
  • A number outside the allowed range.
  • A string sent where a number was expected.

How to fix it as a developer

  • Read the response body: frameworks list every field that failed and why.
  • Return errors per field, so clients can show them next to the right input.
  • Use 400 for bodies that don’t parse at all, and 422 for well-formed data that doesn’t pass the rules.

How to fix it as a visitor

  • Check the form for highlighted fields and correct them, then try again.

Related codes

  • 400 Bad Request: The server can’t or won’t handle the request because something in it is malformed.
  • 409 Conflict: The request clashes with the current state of the resource, such as an edit conflict or a duplicate.
  • 415 Unsupported Media Type: The server doesn’t accept the format of the request body, usually because of the Content-Type header.

Where it’s defined

422 Unprocessable Content is defined in RFC 9110, section 15.5.21. It’s a 4xx code, the client error class: something is wrong with the request, so sending it again unchanged won’t help.

Other 4xx codes

400 Bad Request · 401 Unauthorized · 402 Payment Required · 403 Forbidden · 404 Not Found · 405 Method Not Allowed · 406 Not Acceptable · 408 Request Timeout · 409 Conflict · 410 Gone · 413 Content Too Large · 414 URI Too Long · 415 Unsupported Media Type · 418 I’m a teapot · 429 Too Many Requests · 431 Request Header Fields Too Large · 451 Unavailable For Legal Reasons · 499 Client Closed Request

Or search them all in the HTTP status code list.

Questions people ask

What does HTTP 422 Unprocessable Content mean?
The request is well formed, but the data in it doesn’t make sense, such as failing validation.
What’s the difference between 400 and 422?
400 is for requests the server can’t understand, such as broken JSON. 422 is for requests it understands but can’t accept, such as a valid JSON object with an invalid email in it.
Is 422 only for WebDAV?
Not any more. It started in WebDAV (RFC 4918), and RFC 9110 moved it into core HTTP as “Unprocessable Content”.
↑↓ move↵ openesc close