All templates
Starters
Mock every HTTP error
One endpoint per failure code, so error handling gets tested on purpose.
9 routes · live immediately · no account needed
Most error-handling code is written from imagination and never executed until a real outage runs it for the first time. This mock gives every failure its own address: call /404 to get a 404, /500 to get a 500, /429 to get a rate limit with a Retry-After header. Point your client at each in turn and find out what it actually does.
What you get
GET
/400400 Bad RequestGET
/401401 UnauthorizedGET
/403403 ForbiddenGET
/404404 Not FoundGET
/409409 ConflictGET
/422422 UnprocessableGET
/429429 Too Many RequestsGET
/500500 Server ErrorGET
/503503 UnavailableExample response
GET /400
{
"error": "bad_request",
"message": "The request could not be understood."
}Good for
- Drive every branch of your error handling from a test
- Check that retry and backoff logic reacts to Retry-After
- Demo how the UI degrades when a backend misbehaves