HTTP status code 422 — Unprocessable Entity
Quick answer
Status code 422 (Unprocessable Entity): Valid syntax, but semantic validation failed. Common in APIs for field-level validation errors with a JSON error body.
Common in APIs for field-level validation errors with a JSON error body.
Unlike 400, 422 usually means syntax was fine but business rules failed. Read the error payload for per-field messages.
Common causes
- A field value is syntactically valid JSON but fails a business rule (e.g. end date before start date)
- Uniqueness or cross-field validation failing server-side
How to fix it
Read the per-field error payload most APIs return with 422 and fix the specific field/rule it names.
Related: 418415429413410409500502
Frequently asked questions
What is status code 422?
422 Unprocessable Entity: Valid syntax, but semantic validation failed. Common in APIs for field-level validation errors with a JSON error body.
When should I expect HTTP 422?
Unlike 400, 422 usually means syntax was fine but business rules failed. Read the error payload for per-field messages.
What usually causes HTTP 422?
A field value is syntactically valid JSON but fails a business rule (e.g. end date before start date); Uniqueness or cross-field validation failing server-side.
How do I fix HTTP 422?
Read the per-field error payload most APIs return with 422 and fix the specific field/rule it names.
Where can I see all status codes?
Open the HTTP status codes hub on TryDevSnip for the full reference list.
Does TryDevSnip log my API traffic?
No. These pages are static reference. TryDevSnip does not proxy or inspect your HTTP calls.