Current version
2026-07-02 is the only supported version today. It is marked beta because the API is still evolving. Breaking changes may occur before a stable release. Use the development base URL when testing this version.2026-07-02.
Environment base URLs
Beta API versions are available on development. Live will receive stable versions when they are released.
How version is chosen
When you callPOST /api/auth, the API version is resolved in this order:
api_versionin the auth request body (if provided)- Default version on the API credential
- Recommended version (
2026-07-02)
- Embedded in the JWT as the
api_versionclaim - Returned in the
ST-Api-Versionresponse header on every API response - Marked as beta via
ST-Api-Version-Beta: truefor2026-07-02(development)
Beta indicator header
Responses for beta version2026-07-02 on development include:
Version format
Versions must matchYYYY-MM-DD and be listed in the supported versions set. Requesting an unsupported version returns:
Protected endpoints
Protected routes use the version from the JWT, not from a request header. You cannot change the contract mid-session — obtain a new token with a differentapi_version at auth time.
Adding new versions
When a new API version is released:- A new entry appears in the docs version switcher (with
StableorBetatag as appropriate) - Existing integrations on older versions continue to work until deprecated
Stable releases
When2026-07-02 graduates from beta to stable, the ST-Api-Version-Beta header will no longer be sent for that version. Stable versions will roll out to the live environment.
