Get started
Revisions
The revision header, and which dates this server accepts.
The revision header
Every request names the API revision it was written for, as a date in a revision header. This server implements revision 2026-10-15, and every response carries revision: 2026-10-15.
http
revision: 2026-10-15Which revisions are accepted
| You send | We answer |
|---|---|
2026-10-15 | The request, as documented here |
| An earlier date, such as one your client library pins | The request, with 2026-10-15 behaviour |
A date with a suffix, such as 2026-10-15.pre | Treated like the date alone |
| A date after 2026-10-15 | 404 not_found: that revision is not available here yet |
| A date in the future | 404 not_found |
| Nothing, or not a YYYY-MM-DD date | 400 invalid_revision |
Older revisions
Because earlier dates get 2026-10-15 behaviour, a client pinned to an older revision keeps working as long as it does not rely on something that changed between its revision and ours. Send
2026-10-15 in new code.When a newer revision arrives
We add a revision when this server implements it, and the changelog records it. The revision picker at the top of these pages sets the date the code samples send: 2026-10-15 or 2026-04-15.