Last-Modified
Declared by 43 providers across 2512 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.
Last-Modifiedlast-modified
The registry
| Status | permanent |
|---|---|
| Reference | RFC 9110, Section 8.8.2: HTTP Semantics |
Providers declaring it (43)
acronis adp airbus-oneatlas amazon-s3 apache-ozone autodesk-fusion avito brightcove btc-war-live-market-data-api ccp-games cloudflare-r2 cubefs deliverect dotdigital eclipse etsi euronet eve-online game-of-thrones here honeycomb-io instabase lakefs lichess microsoft-azure microsoft-azure-batch nasuni newstore nhost oracle oracle-cloud oracle-database oracle-platforms qliksense salesforce sovrn stanford viglink wikidata wikimedia wikipedia wso2 zhejiang
Explore
All headers Conditional Requests & Concurrency 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.