Problem Details Test API

This service provides test endpoints that return structured error responses in the application/problem+json format, as defined in RFC 7807. It's useful for developers testing HTTP clients, middleware, error handling, logging, and observability pipelines.

Endpoints

Each of these returns a Problem Details JSON object with a relevant HTTP status code:

• /problem – 400 Bad Request for invalid input
• /problem/unauthorized – 401 Unauthorized to test auth logic
• /problem/not-found – 404 Not Found when a resource is missing
• /problem/validation-error – 400 with structured field-level errors
• /problem/server-error – 500 Internal Server Error simulation
• /problem/too-many-requests – 429 Too Many Requests for rate limiting

What is Problem Details?

Problem Details is a standardized way to express HTTP API errors using a machine-readable JSON format. Introduced in RFC 7807, it aims to replace ad-hoc error structures and magic strings in APIs.

Each error response contains a consistent set of fields:

• type: A URI identifying the kind of error (ideally documentation or a standard identifier)
• title: A short human-readable summary
• status: HTTP status code (e.g. 404)
• detail: A detailed explanation for debugging purposes
• instance: A URI identifying the specific occurrence (like a trace ID or log link)

Here’s a typical Problem Details response:

{
  "type": "https://example.com/errors/invalid-input",
  "title": "Invalid input",
  "status": 400,
  "detail": "The 'email' field is required and must be a valid email address.",
  "instance": "/users/register"
}

And a validation error example with extended fields:

{
  "type": "https://example.com/errors/validation",
  "title": "Validation Failed",
  "status": 400,
  "detail": "Multiple validation errors occurred.",
  "instance": "/signup",
  "errors": {
    "email": ["Email is required.", "Email must be valid."],
    "password": ["Password must be at least 8 characters."]
  }
}

Why use this site?

If you're building HTTP APIs or consuming them, this service helps you:

• Validate client behavior under error conditions
• Simulate various HTTP errors in CI tests
• Evaluate logging or alerting strategies with predictable payloads
• Train developers or QA on error structure