The Repeatability-Result HTTP header — idempotency & reliability, declared by 1 providers in the API Evangelist catalog.
Repeatability-Result
Idempotency & Reliability IANA provisional response
A reference entry. The registry facts and catalog measurements below are complete; the written guidance for this header has not been authored yet.
Repeatability-Result is idempotency & reliability — Headers that make a retry safe. Almost entirely a payments-industry invention that the rest of the API economy has not adopted.
The registry
Listed in the IANA HTTP Field Name Registry as a provisional entry — registered, but not through a standards-track document. Defined in Repeatable Requests Version 1.0][OASIS][Chet_Ensign.
In the catalog
Declared by 1 providers across 37 published specification files in the API Evangelist catalog, where it appears as a response header — sent by the server.
Governed by these rules
Machine-enforceable governance rules from rules.apievangelist.com that apply to this header when it appears in an OpenAPI.
OpenAPI Components Headers Error error
Utilizing the headers object in the centralized OpenAPI components library helps make headers reusable across API requests and responses
Guidance: Rate Limits →OpenAPI Components Headers Info info
Utilizing the headers object in the centralized OpenAPI components library helps make headers reusable across API requests and responses
Guidance: Rate Limits →OpenAPI Headers Hyphenated Pascal Case error
HTTP headers should follow Hyphenated-Pascal-Case naming convention for consistency and readability, such as Content-Type, X-Request-Id, or Accept-Language.
Guidance: Naming →