415 vs 422: Unsupported Media Type vs Unprocessable Content
415 and 422 can look similar in logs, but they tell clients, crawlers, and API consumers different things.
| Aspect | 415 | 422 |
|---|---|---|
| Meaning | Unsupported Media Type describes how the server processed the request and what the client should do next. | Unprocessable Content describes how the server processed the request and what the client should do next. |
| Typical use case | HTTP 415 Unsupported Media Type indicates a client errors response outcome. | HTTP 422 Unprocessable Content indicates a client errors response outcome. |
| Caching/client behavior | Check cache headers and downstream behavior for 415. | Check cache headers and downstream behavior for 422. |
| SEO implications | Search crawlers interpret 415 according to client-errors semantics. | Search crawlers interpret 422 according to client-errors semantics. |
| API/backend impact | API clients may branch logic specifically on 415. | API clients may branch logic specifically on 422. |
When to use one vs the other
Use 415 when the response should communicate unsupported media type behavior; use 422 when unprocessable content is the accurate protocol signal.
A frequent mistake is swapping 415 and 422 for convenience; that causes client retry bugs, incorrect cache signals, and misleading monitoring data.
Decision summary: if user agents should receive the Unsupported Media Type signal, return 415; if they should receive Unprocessable Content, return 422.
FAQ
What is the biggest difference between 415 and 422?
415 communicates Unsupported Media Type, while 422 communicates Unprocessable Content. Choosing the right one keeps clients and intermediaries predictable.
Do 415 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 415 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.
Related guides: 415 Unsupported Media Type · 422 Unprocessable Content