Date
Declared by 50 providers across 3934 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.
Datedate
The registry
| Status | permanent |
|---|---|
| Reference | RFC 9110, Section 6.6.1: HTTP Semantics |
Providers declaring it (50)
adobe-suite aeropay aimlapi api-pulse apiops-cycles-canvas bird bitpowr-technologies-inc blnkfinance brightcove chaitin cisco-meraki cisco-secure-firewall cisco-umbrella citi conekta deliverect deluxe extreme-networks finix finix-payments fintecture hipay infisical interchecks kudosity lemlist linkedin london-stock-exchange-group messaging-api microsoft-azure mparticle nasuni orders-api persons-api products-api rhombus-systems salesforce satispay shopback shyft sofi-technologies streamelements tetrascience tribe-payments unified-to upwind userpilot vtex xflow zoominfo
Explore
All headers Representation Metadata 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.