409 vs 422: Conflict vs Unprocessable Content
409 and 422 can look similar in logs, but they tell clients, crawlers, and API consumers different things.
| Aspect | HTTP 409 — Conflict | HTTP 422 — Unprocessable Content |
|---|---|---|
| Definition | Often seen in REST APIs when a PUT or POST violates a uniqueness constraint or tries to create a resource that already exists. | The server understands the Content-Type and the request is well-formed, but cannot process it due to semantic errors. Common in REST API validation failures. |
| Plain-language summary | The request conflicts with the current state of the resource. Most common in REST APIs when trying to create a resource that already exists, or when concurrent edits produce a version mismatch. The response body should explain what the conflict is. | The request body is syntactically valid (it parsed successfully) but semantically invalid — the content violates business rules or data constraints. The most common use is REST API field validation failures. |
| When to use | Return 409 when the request is syntactically valid but conflicts with an existing resource state — duplicate email, concurrent edit conflict, version mismatch. Use 422 for semantic validation failures unrelated to conflicts. Include enough detail in the response body for the client to resolve the conflict. | Return 422 when the body was parsed correctly but failed validation: required field present but empty, value out of allowed range, date in the past when future is required, or custom business rule violation. Use 400 for parsing failures (malformed JSON, wrong Content-Type). Use 409 for conflicts with existing resource state. |
| Client behavior | Do not auto-retry. Resolve the conflict (e.g., fetch the current state and re-apply changes) before retrying. | Do not auto-retry. Fix the payload based on the validation errors in the response body. Implement client-side validation to prevent 422s before the request is sent. |
| Caching behavior | Not cached. | Not cached. |
| SEO / crawler impact | Search crawlers interpret 409 (client-errors) for indexation and link equity accordingly. | Search crawlers interpret 422 (client-errors) for indexation and link equity accordingly. |
| API / backend impact | API clients branching on 409 expect Conflict semantics. | API clients branching on 422 expect Unprocessable Content semantics. |
| Safe to retry? | Only after fixing the underlying cause | Only after fixing the underlying cause |
Common real-world scenarios
When you see HTTP 409
Common in registration flows (duplicate email), collaborative editing (optimistic locking), and idempotency enforcement. Spikes in 409 indicate concurrency issues in the application layer.
When you see HTTP 422
In form-heavy APIs, high 422 rates indicate: poor client-side validation that lets invalid data reach the server, mismatch between frontend and backend validation rules, or an API schema change that old clients have not adopted.
Decision rule
Use 409 when the response should communicate conflict behavior; use 422 when unprocessable content is the accurate protocol signal.
A frequent mistake is swapping 409 and 422 for convenience; that causes client retry bugs, incorrect cache signals, and misleading monitoring data.
Use 409 when the correct protocol signal is Conflict. Use 422 when the correct signal is Unprocessable Content. Returning either code for the wrong reason breaks client expectations, cache behavior, and monitoring accuracy.
FAQ
What is the biggest difference between 409 and 422?
409 communicates Conflict, while 422 communicates Unprocessable Content. Choosing the right one keeps clients and intermediaries predictable.
Do 409 and 422 have SEO or caching impact?
Yes. Search engines and caches interpret status classes differently. Use each code according to its semantics to avoid accidental indexing, stale responses, or crawl inefficiency.
Can APIs safely return 409 instead of 422?
Only when it matches contract semantics. API clients often branch logic by exact code, so swapping them can break retries, auth handling, or user-facing errors.
Full guides
HTTP 409 Conflict — full guide · HTTP 409 status reference · HTTP 422 Unprocessable Content — full guide · All comparisons · HTTP 422 status reference