Design and review RFC 9457 problem details error responses for HTTP APIs.
npx skills add https://github.com/DeepSpaceCartel/skills --skill rfc9457-deepspacecartel
Please help me install this Agent Skill. Skill: rfc9457 Source: https://github.com/DeepSpaceCartel/skills/tree/main/skills/rfc9457 Command: npx skills add https://github.com/DeepSpaceCartel/skills --skill rfc9457-deepspacecartel
High-intent search queries and answers about installing and using this skill.
Return a JSON body with media type application/problem+json containing the members type, status, title, detail, and instance. All five are optional; an omitted type defaults to about:blank, meaning no semantics beyond the HTTP status code.
RFC 9457 obsoletes RFC 7807 but keeps the same media types and wire format, so existing RFC 7807 responses remain valid RFC 9457 responses. The update mainly clarifies guidance on extensions, security, and type definition.
Add extension members beyond the five core fields, documented by your problem type, such as an errors array with detail and pointer entries for validation failures. Consumers must ignore extensions they do not recognize, so types can evolve safely.
Avoid it when a bare status code already explains the condition, when the response is a normal resource representation, or when your API already has an application-specific error format. Never use it as a channel for stack traces or debugging internals.
The status member is advisory and exists only so consumers can recover the original code after an intermediary changes it. A mismatch signals that something in the path altered the response, so the two must never intentionally differ.
goodstoriesworldDesign consistent REST and GraphQL APIs with OpenAPI specifications.
asterdexInterpret Aster Futures API v1 error codes and rate limits.
rizwan2004csDesign REST API conventions and OpenAPI documentation for backend services.
twhitehead-blackdogDiagnose People application errors using console logging and Chrome DevTools.
