HTTP 422 Unprocessable Content

The syntax is fine and the server understood the request, but the content is semantically wrong — a valid date in the past where a future one is required, a transfer that would overdraw an account.

Why you would test it

The distinction from 400 is the point: 400 means "I could not read this", 422 means "I read it, and no". Clients should surface them to users differently.

Endpoints that return 422

14 endpoints in this playground answer with 422. Every one is free, needs no signup, and can be called from the browser or with curl.

Other client error codes

All HTTP status codes · All 37 mock REST APIs · Getting started guide