/v1 and the agent session endpoints live under /v2. Integrations built against a major version keep working for as long as that version is supported.
What can change within a version
Within a major version we only make additive changes, such as new endpoints, new optional request fields, new response fields and new enum values. Write clients that ignore fields they don’t recognize so these changes never break you. Anything that would break an existing client ships under a new major path, for example/v2, while the old path keeps working. That covers removing or renaming a field, changing a type or tightening validation.
How deprecations are announced
When we plan to retire an endpoint or a major version, we announce it in the changelog and on this page. Responses from the deprecated operation then carry these headers:
A deprecated operation keeps working for at least 90 days after the
Deprecation header first appears, and the Sunset date is never earlier than that.
Current deprecations
None. No/v1 or /v2 operation is scheduled for removal.
Next steps
Getting started
Explore the endpoint groups
Rate limits
Limits and the headers that report them