Prefer
Declared by 37 providers across 642 published specification files in the APIs.io network.
Spelled 2 ways
HTTP field names are case-insensitive (RFC 9110 §5.1), so every spelling below is the same header on the wire. A contract is not the wire: generated clients key off the string, and a developer reading two of these sees two different headers.
Preferprefer
Reached by regulation
cms-interoperability-prior-authorization 21st-century-cures-act
Carried by the fhir-bulk-data standard.
The registry
| Status | permanent |
|---|---|
| Reference | RFC 7240: Prefer Header for HTTP |
Providers declaring it (37)
adp advancedmd anyapi aptible athenahealth cadasto cdk-global cms cms-gov cognite ehrbase gc-ai gonitro insforge intersight jefferson-health microsoft-azure microsoft-dynamics-365 microsoft-dynamics-365-sales microsoft-power-apps morningstar nextgen-healthcare openehr oracle-weblogic paypal postman quinyx refinitiv replicate resemble-ai specterops supabase temple-health vastdata visier vitagroup wmo
Explore
All headers Async & Long-Running Guidance on headers.apievangelist.com
Work with this as data
Every header here is available over the APIs.io API and to AI agents over MCP. HTTP Headers is not yet its own endpoint on the v1 API. Reach it through catalog search and the tag graph, or the MCP server.