What Is HTTP 422 Unprocessable Entity?
HTTP 422 Unprocessable Entity explained, and what it means when you see it in CI/CD and deployments.
HTTP 422 means the syntax is valid but the content failed semantic validation.
What it means
A 422 differs from 400: the JSON parses fine, but a field violates a rule (missing required value, out of range, wrong format). APIs return validation details in the body.
When you see it in CI/CD
In CI, a 422 from an API test means the payload is structurally valid but semantically wrong. Read the error body to see which field failed.
Key takeaways
- 422 means validation failed.
- Syntax is fine; a value is invalid.
- Read the body for field-level errors.
Related guides
What Is HTTP 400 Bad Request?HTTP 400 Bad Request means the server could not understand the request. Learn common CI causes.
What Is Data Validation? Checking Data Quality ExplainedData validation explained: the automated checks that confirm data meets expectations on shape, type, and rang…
What Is a REST API? Resource-Oriented Web APIsA REST API exposes resources over HTTP using standard methods and status codes. Learn what REST is and how CI…