Mock HTTP Status Response Generator

How to use

1. 1️⃣
   Choose your options above
2. 2️⃣
   Click Generate
3. 3️⃣
   Copy your result

Detailed instructions

1. Select a Status Group from the dropdown — choose 'Any' for a mixed set or a specific group like '4xx Client Error' to focus your test batch.
2. Set the count field to how many mock responses you need, typically three to five for a test suite or one to two for documentation.
3. Click Generate to produce the mock HTTP responses, each showing the status line, headers, and JSON body.
4. Copy individual responses and paste the JSON body into your test fixture, mock server, or API documentation as needed.
5. Regenerate as many times as needed to get varied status codes within the same group for broader test coverage.

Use Cases

• •Populating Postman mock servers with realistic 4xx and 5xx response bodies
• •Writing Jest or Vitest unit tests that assert correct handling of 401 Unauthorized
• •Seeding Storybook stories with varied HTTP error states for UI component testing
• •Generating API documentation examples covering both 2xx success and 4xx failure paths
• •Testing exponential backoff and circuit breaker logic using batches of 5xx responses

Tips

• →When testing retry logic, generate five or more 5xx responses at once to get varied codes like 500, 502, 503, and 504 in one batch.
• →Pair a generated 401 body with a 200 body to build realistic login-flow tests that cover both authenticated and unauthenticated states.
• →For API docs, always include at least one 4xx and one 5xx example alongside your 2xx success response — readers need to see failure modes.
• →The X-Request-ID in the headers is a useful field to reference in your error handling UI — show it in error messages so users can report it.
• →When using responses in Storybook, create one story per status group so each UI error state has a dedicated, reproducible example.
• →If your API uses 422 Unprocessable Entity for validation errors, filter to 4xx and look for 422 responses — their bodies typically include a field-level errors array you can adapt.

FAQ