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 Request
GET/401401 Unauthorized
GET/403403 Forbidden
GET/404404 Not Found
GET/409409 Conflict
GET/422422 Unprocessable
GET/429429 Too Many Requests
GET/500500 Server Error
GET/503503 Unavailable

Example 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