422 Unprocessable Content
The body is well-formed but semantically invalid.
What it means
The JSON parsed fine, but values break business rules, such as an end date before the start date.
What your client should do
Read the field errors, fix the values, and send again.
Should you retry?
Only after you change the request.
Try it
The free practice API returns this status on demand, with the headers a well-behaved API would send. Call GET /api/play/status/422 from Endpoint Client and open the Explain tab.
Related codes
400 Bad Request
The server cannot process the request as sent.
409 Conflict
The request conflicts with the current state of the resource.
Defined in RFC 9110. All status codes and headers