When should an API return 400 versus 422?
400 means the request is malformed in a way the server could not parse, such as broken JSON. 422 Unprocessable Content means the request was well-formed but failed semantic validation, like an invalid email or a negative quantity. Many APIs use 400 for both, but separating them helps clients.
Answered in
HTTP Status Codes You Misuse, and What to Return Instead401 vs 403, 301 vs 308, 404 vs 410, 502 vs 503 vs 504. Picking the right status code tells clients and monitors what to do next.
Read the full analysisOther questions this article answers
More development best practices questions
- What is the primary security vulnerability of storing JWTs in localStorage?
- How do server-side sessions scale horizontally across multiple instances?
- Why is immediate revocation nearly impossible with stateless JWTs?
- What is the recommended modern authentication architecture for SaaS apps?
- What is the N+1 query problem in GraphQL and how is it fixed?
- How does GraphQL Federation allow multiple backend teams to maintain one API?
- Why is caching harder in GraphQL than in traditional REST APIs?
- When should an engineering team prefer REST or gRPC over GraphQL?
Every answer on Crashtech is written by the editor of the article it comes from — never auto-summarised. Browse all answers or the Development Best Practices beat.