Documentation
Versioning
Each API version is named after the month it was released, in YYYY-MM form, and is part of
the request URL:
Code
There is no latest alias: every request names its version. Your integration keeps working
against the version it was built for, and moving to a newer version is always a change you make.
Breaking changes only ship in a new version. A version's status changes its documentation, never its endpoints.
Version status
| Status | Meaning |
|---|---|
| Current | The version for new integrations. There is exactly one. |
| Release candidate | The next version. It is already served, but its endpoints may still change until its planned release day. |
| Deprecated | Still served until it is removed after its removal deadline. Move to the release candidate, or to the current version when there is none. |
Available versions
| Version | Status | Released | Notes |
|---|---|---|---|
2025-03 | Current | 7 Mar 2025 | The version for new integrations. |
2026-11 | Release candidate | 30 Nov 2026 (planned) | Release candidate, planned for release on 30 November 2026. Its endpoints may still change until then. |
2025-11 | Deprecated | 15 Nov 2025 | Deprecated. This version will be removed on 28 February 2027. Move to 2026-11, planned for release on 30 November 2026. |
Use the version dropdown in the API Reference to switch between versions.
Last modified on