A problem response
01A JSON problem object provides machine-readable error information alongside an HTTP status.
Related RFCs and changes
“Updates” changes part of an earlier RFC. “Obsoletes” replaces it. This list shows selected related documents.
DIAGRAM§ 3 ↗
RFC 9457 · § 3EXAMPLE
3 / 3
03
Interpret both layers
Generic HTTP software reads the status; clients may use the structured details.
Protocol participantThreat or exceptionProtocol controlSimplified drawings · precise section references
RFC 7807RFC 9457 Appendix D
The revision adds a registry of common problem type URIs and clarifies multiple-problem handling and type-URI guidance.
Read the updated RFC section ↗Use application/problem+json for the JSON format.
- Use application/problem+json for the JSON format.
- Problem details complement HTTP status semantics rather than redefining them.
- The status member, if present, must match the status generated in the HTTP response.
Examples are illustrative. Consult the linked RFC and its errata for implementation details.
Read the RFC section ↗Diagrams simplify the RFC. Read the linked sections for complete requirements.
Privacy