HTTP 412 Precondition Failed

A condition in the request headers was not met — almost always an If-Match ETag that no longer reflects the current state of the resource.

Why you would test it

The core of optimistic concurrency. If you never see a 412 in testing, your client is probably not sending If-Match at all, and lost updates are going unnoticed.

Endpoints that return 412

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

…and 5 more endpoints across the catalog.

Other client error codes

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