Skip to main content
The API uses a staged versioning strategy.

beta — today

beta is a rolling channel that always points at the latest not-yet-official version. While in beta we co-design the API with early adopters, so breaking changes can happen on this path. We’ll flag them in advance to active users.

v1 — at GA

When the surface stabilizes, we promote it to a stable version:
From v1 onward we follow an additive-compatibility contract: we may add fields and endpoints, but we won’t remove or repurpose existing ones without a new major version.

Recommendation

Use beta to explore, integrate early, and send us feedback — but treat it as pre-production: it isn’t intended for production workloads, and breaking changes can land without a version bump. If you need long-term stability guarantees, wait for v1 and pin to it once it ships.