DevArbor
4xx Client Error

422 Unprocessable Entity

What it means

The server understands the request format (the syntax is valid JSON, for example) but the content itself fails validation. Unlike 400 (malformed), 422 means "I can read this, but the values don't make sense" — like a valid JSON body with an invalid email address.

Site Visitor

What can I do?

  • Check the URL for typos — a single wrong character causes most 4xx errors.
  • Try navigating to the site's homepage and searching from there.
  • If the problem persists after retrying, contact the site owner.
Developer

How to debug & fix

  1. Return 422 with detailed validation errors in a structured format
  2. FastAPI returns 422 automatically for Pydantic validation errors
  3. Include field-level error messages: {"errors": [{"field": "email", "message": "invalid format"}]}
  4. Return structured per-field errors so clients can highlight specific form fields: {"errors":[{"field":"email","message":"invalid format"}]}.

Code Example

Node.js / Express
app.post('/events', (req, res) => {
  const { startDate, endDate } = req.body;
  if (new Date(endDate) <= new Date(startDate)) {
    return res.status(422).json({
      errors: [{ field: 'endDate', message: 'Must be after startDate' }]
    });
  }
});

Related Status Codes

400 Bad Request 409 Conflict

How HTTP Status Codes Work

Every HTTP response carries a three-digit status code that tells the client — browser, API consumer, or search-engine crawler — exactly what happened. The first digit defines the class: 1xx informational (request in progress), 2xx success, 3xx redirection, 4xx client error (bad request, missing auth, not found), and 5xx server failure.

Status codes are standardised in RFC 9110 (HTTP Semantics, 2022). Extensions like WebDAV (RFC 4918) and rate-limit headers (RFC 6585) added codes beyond the core set. When a client receives an unrecognised code, the rule is to treat it as the generic x00 of its class.

Why the Right Code Matters

Semantically correct codes help search engines index accurately (301 passes link equity; 410 removes pages faster than 404), allow API clients to implement correct retry logic (429 + Retry-After, 503 + Retry-After), and let monitoring systems distinguish bugs (500) from load issues (503) from auth failures (401/403).

Looking up a different status code? The full reference covers all HTTP codes with causes, fix guides, and copyable code examples for Node.js and Python.

Browse the full HTTP Status Code reference →

Frequently Asked Questions

What does HTTP 422 Unprocessable Entity mean?
The server understands the request format (the syntax is valid JSON, for example) but the content itself fails validation. Unlike 400 (malformed), 422 means "I can read this, but the values don't make sense" — like a valid JSON body with an invalid email address.
Is HTTP 422 the visitor's fault?
HTTP 422 Unprocessable Entity is generally a client-side error, meaning the request itself has an issue. However, many causes — such as a broken link on the site or a misconfigured redirect — are the website owner's responsibility, not the visitor's.
How do I fix HTTP 422 Unprocessable Entity?
As a visitor: check the URL for typos, go to the homepage, or search for the content. As a developer: return 422 with detailed validation errors in a structured format.