Reference
API Versioning
Every route is stamped with a year-month version, e.g. /api/2026-06/....
The current — and so far only — version is 2026-06.
Additive changes don't bump the version
Most changes are additive and ship without a new version at all — you'd never need to update your integration for them.
Ships without a version bump
New optional fields on a response, new endpoints, new optional request parameters.
Requires a new version
Removing or renaming a field or endpoint, changing a field's type, changing an HTTP method or status code, changing auth requirements.
When a breaking change does ship
New version introduced
→
old version stays live 90 days
→
responses carry Deprecation + Sunset headers
→
old version retired
| Header | Meaning |
|---|---|
| Deprecation: true | This route is on a deprecated version — start planning a migration. |
| Sunset: <RFC 1123 date> | The exact date the deprecated version stops being served, always 90 days out from deprecation. |
Because there's only ever been one version so far, no request today actually carries these
headers — nothing has been deprecated yet. This page describes the policy that takes effect
the moment a second version ships, so you know what to expect in advance rather than being
surprised by it.