---
title: "422 Unprocessable Entity"
canonical: "https://lemwatch.com/http-status-codes/422"
category: "client-error"
last_verified: "2026-08-11"
source: "https://lemwatch.com"
---

# HTTP 422 Unprocessable Entity

**Summary** — The server understands the request but cannot process the contained instructions.

## What it means

HTTP 422 Unprocessable Entity means the request was well-formed (valid JSON, proper syntax) but semantically incorrect. For example, trying to set an email field to a non-email value, or creating a resource with conflicting data.

## Common causes

- Validation errors (invalid email, short password)
- Business logic violations
- Conflicting data in the request
- Missing required business fields

## How to fix

- Review validation error messages in the response body
- Ensure data meets business rules
- Check required field formats

## SEO impact

No direct SEO impact. Used primarily for API/form validation.

## Monitoring tip

LemWatch can track 422 error rates on your API endpoints. Spikes may indicate a frontend bug sending invalid data.

**Related:** [400](https://lemwatch.com/http-status-codes/400.md), [409](https://lemwatch.com/http-status-codes/409.md)

_Canonical HTML page: https://lemwatch.com/http-status-codes/422_