Async & Long-Running
Headers for work that does not finish inside the request: preference for async handling, polling locations, progress, retry timing.
5 headers, ordered by how many providers in the catalog declare them.
Prefer
37 providers
regulated
2 spellings
How a client asks for async handling. Mandated in the FHIR bulk-data flows that the CMS interoperability rules require.
Content-Location
19 providers
regulated
2 spellings
The Content-Location HTTP header — async & long-running, RFC 9110, declared by 19 providers in the API Evangelist catalog.
Last-Event-ID
9 providers
The Last-Event-ID HTTP header — async & long-running, declared by 9 providers in the API Evangelist catalog.
Preference-Applied
4 providers
The Preference-Applied HTTP header — async & long-running, RFC 7240, declared by 4 providers in the API Evangelist catalog.
Status-URI
1 providers
The Status-URI HTTP header — async & long-running, RFC 2518, declared by 1 providers in the API Evangelist catalog.