--- layout: default ---
Tracing & Correlation

X-Request-Id

de facto — unregistered response 3 spellings

Declared by 68 providers across 8545 published specification files in the APIs.io network.

What this header is for, and how to use it →

A count here is providers whose published contract declares this header — not providers who send it. Response headers set at the edge rarely appear in an OpenAPI at all, so a low number can measure documentation practice rather than deployment.

Spelled 3 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.

X-Request-IdX-Request-IDx-request-id

Providers declaring it (68)

8x8 adobe adobe-creative-cloud appsmax-rest-api-v1 avora-agent-forge bmo cashfree cdk-global censys chamber chargy chariot clearbank conjur coveo currencycloud deepgram digital-ocean etoro euler ex-human exa-ai finix finix-payments fintecture fireblocks godaddy gp-connect healthsherpa kpn kyber-network liberty-global mastercard mercado-pago mercedes-me national-weather-service nexthink nfon nhs-digital nhs-england noaa noaa-gov oracle-hospitality pure-storage salesforce shyft six-group smallstep snapapi-pics stayingapi synack syniverse tickitto tribe-payments triodos-bank-uk truth-systems userpilot vicai voltair weather-gov wordline workstream xquik-api zamna zededa zenrows zero-hash zoominfo

Explore

All headers Tracing & Correlation Guidance on headers.apievangelist.com