422 Unprocessable Content — Causes & Fix
HTTP 422 (Unprocessable Content) means the request was well-formed but the server can't process it because the content failed validation (semantic errors).
- Applies to
- Any website or web server (HTTP standard)
- Time to fix
- 5–30 minutes
What it means
Causes include validation failures — a missing required field, a value out of range, or data that breaks business rules. HTTP status 422 is defined in RFC 9110 (HTTP Semantics). This is a client-side (4xx) error — the request itself had a problem, so the fix is usually on the requester's side or in how the server validates the request.
Symptoms
- "422 Unprocessable Entity/Content" from an API
- A form/API submission is rejected despite valid JSON
How to fix it
- 1
Fix the invalid fields
1. Read the error details — they usually name which field failed validation — and correct it.
- 2
Match the schema (developers)
1. Ensure all required fields are present and values meet the API's rules.
Frequently asked questions
422 vs 400?
400 means the request is malformed (bad syntax); 422 means the syntax is fine but the data failed validation. Fix the specific field the API flags.
Last updated July 20, 2026
Guidance only — always consult a qualified professional or the official service manual before carrying out repairs.