Get a sample RFC 7807 problem document
The status code matches the problem. 401 adds WWW-Authenticate; 429 and 503 add Retry-After.
Parameters 1
| Name | Type | Description |
|---|---|---|
typerequired | path · string | bad-request, unauthorized, payment-required, forbidden, not-found, conflict, validation, rate-limited, internal or unavailable (case-insensitive). |
Responses
- 200
- Never returned: every sample uses its own error status.
- 404
- Unknown problem type.
Example
Request
curl -X GET "https://api.testingapis.com/api/validation/problem/bad-request" \
-H "X-TestingApis-Key: YOUR_API_KEY"Response400 Bad Request
Content-Type: application/problem+json; charset=utf-8
{
"type": "https://example.com/problems/bad-request",
"title": "Bad Request",
"status": 400,
"detail": "The request body could not be parsed as JSON.",
"instance": "/api/validation/problem/bad-request",
"traceId": "00-4bf92f3577b34da6a3ce929d0e0e4736-00f067aa0ba902b7-01",
"line": 3,
"column": 14
}Sign in to see the details
The parameters, request and response examples and the live Try it panel for this endpoint are for signed-in members. Accounts are free and take a few seconds to create.