Compare Status Codes
Select up to 3 status codes to compare side-by-side
🤨400Bad Request
🤔422Unprocessable Entity
| 🤨 400 | 🤔 422 | |
|---|---|---|
| Name | Bad Request | Unprocessable Entity |
| Category | 4xxClient Error | 4xxClient Error |
| Description | The server cannot process the request due to client error (malformed syntax, invalid request framing, etc.). | The request was well-formed but was unable to be followed due to semantic errors. |
| When to Use |
|
|
| Common Causes |
|
|
Description
The server cannot process the request due to client error (malformed syntax, invalid request framing, etc.).
When to Use
- Request is syntactically malformed (invalid JSON, wrong content-type)
- Required parameters are missing entirely
- Use 422 instead when syntax is valid but semantically incorrect
Common Causes
- Malformed JSON in request body
- Missing required fields
- Invalid query parameters
Description
The request was well-formed but was unable to be followed due to semantic errors.
When to Use
- Request is syntactically valid but fails semantic validation
- Form field validation errors (invalid email, password too weak)
- Business logic violations (date in past, negative quantity)
Common Causes
- Validation errors in request body
- Semantically incorrect data
- Business logic validation failed