API Design

API Error Format Checker

Paste an API error response JSON to validate against RFC 7807 Problem Details format, check for information disclosure risks, and validate field-level error structure.

Calculations run locally in your browser

API Error Format Checker

The API Error Format Checker validates error JSON against RFC 7807 Problem Details format, detecting stack trace exposure, missing machine-readable codes, and field-level validation error structure.

โ€ข Validate an error response format before publishing to an API spec

โ€ข Check whether a validation error response includes field-level details

โ€ข Detect stack traces in error responses that expose implementation details

โ€ข Ensure error responses use machine-readable codes alongside human-readable messages

Continue with Utility Matrix tools for the next decision in this workflow.
Browse tools โ†’
What does this tool tell you?
The API Error Format Checker validates error JSON against RFC 7807 Problem Details format, detecting stack trace exposure, missing machine-readable codes, and field-level validation error structure.
What affects the result most?
RFC 7807 Problem Details: type (URI), title (human-readable), status, detail, instance fields. Content-Type for errors: application/problem+json โ€” distinct from application/json for error detection. Error envelope pattern: {error: {code, message, details}} โ€” common but non-standard.
How should I use the result?
Treat the tool's output as a first-pass check, not a proof of correctness. A clean pass means no issues in the patterns this tool recognizes; a failure points to a specific problem you can investigate in your source. The underlying spec is the authoritative source for edge cases.