---
title: "HTTP 422 Unprocessable Entity — Meaning & Fix"
description: "HTTP 422 Unprocessable Entity explained: what it means, common causes, how to fix it and how to monitor for it."
url: https://uptrack.app/http/422
---

# HTTP 422 Unprocessable Entity

The server understands the request format but cannot process the contained instructions. The syntax is correct (not a 400), but the content fails semantic validation — like submitting a form with an invalid email address.

## What does HTTP 422 mean?

The server understands the request format but cannot process the contained instructions. The syntax is correct (not a 400), but the content fails semantic validation — like submitting a form with an invalid email address.

## Common causes

1. 1  
Form validation failed — required fields are missing, an email format is invalid, a number is out of range, or a string exceeds the max length.
2. 2  
Business logic validation failed — for example, setting an end date before the start date, or referencing a foreign key that does not exist.
3. 3  
The request body is syntactically valid JSON but contains fields with the wrong data types (string instead of number, null where required).

## How to fix it

1. 1  
Read the response body. APIs that return 422 almost always include field-level error messages explaining what failed validation.
2. 2  
Add client-side validation to catch these errors before submitting. Validate required fields, formats, and ranges in the form.
3. 3  
If the validation rules changed server-side, update your client to match the new requirements. Check API changelog or documentation.

## Monitor for HTTP 422 errors

A spike in 422 errors from your API may mean validation rules changed in a deploy and clients are sending data the server now rejects. Uptrack helps you catch these regressions.

## Catch HTTP errors before your users do

Start free, or choose a plan, for 30-second monitoring and alert confirmation.

[See plans](https://uptrack.app/pricing)

from $3/mo · 30-day money-back guarantee

## Other HTTP status codes

- [HTTP 415 Unsupported Media Type](https://uptrack.app/http/415)
- [HTTP 429 Too Many Requests](https://uptrack.app/http/429)
- [HTTP 413 Payload Too Large](https://uptrack.app/http/413)
- [HTTP 410 Gone](https://uptrack.app/http/410)
- [HTTP 409 Conflict](https://uptrack.app/http/409)
- [HTTP 408 Request Timeout](https://uptrack.app/http/408)
- [HTTP 405 Method Not Allowed](https://uptrack.app/http/405)
- [HTTP 404 Not Found](https://uptrack.app/http/404)
- [HTTP 403 Forbidden](https://uptrack.app/http/403)
- [HTTP 401 Unauthorized](https://uptrack.app/http/401)
- [HTTP 400 Bad Request](https://uptrack.app/http/400)
- [HTTP 451 Unavailable For Legal Reasons](https://uptrack.app/http/451)
- [HTTP 500 Internal Server Error](https://uptrack.app/http/500)
- [HTTP 502 Bad Gateway](https://uptrack.app/http/502)
- [HTTP 503 Service Unavailable](https://uptrack.app/http/503)
- [HTTP 504 Gateway Timeout](https://uptrack.app/http/504)
- [HTTP 520 Web Server Returns Unknown Error](https://uptrack.app/http/520)
- [HTTP 522 Connection Timed Out](https://uptrack.app/http/522)
- [HTTP 304 Not Modified](https://uptrack.app/http/304)
- [HTTP 302 Found](https://uptrack.app/http/302)
- [HTTP 301 Moved Permanently](https://uptrack.app/http/301)
- [HTTP 204 No Content](https://uptrack.app/http/204)
- [HTTP 201 Created](https://uptrack.app/http/201)
- [HTTP 200 OK](https://uptrack.app/http/200)
