Should I move my API error bodies to the RFC 7807 problem+json format?
Standardize on RFC 9457 rather than 7807, produce every error body in one central exception handler, and manage the `type` URI as a versionable contract.
Tag
REST and modern API design: contracts, versioning, error shape and consumption practices. Questions under this tag, answered directly.
4 answered questions carry this tag.
Standardize on RFC 9457 rather than 7807, produce every error body in one central exception handler, and manage the `type` URI as a versionable contract.
Go contract-first with `openapi.yaml` as the single source of truth; what ends drift isn't the direction you pick but a green contract test running in CI.
Instrument usage per partner, publish a dated sunset with Sunset and Deprecation headers on every response, run brownouts, and cut when usage nears zero.
Verify the HMAC constant-time over the raw body, return 200 fast and enqueue the work, and let a UNIQUE constraint on event_id enforce once-only.