Changelog

Every change to the public v1 contract is reviewed against the compatibility policy before it ships. Additive changes - new endpoints, new optional request fields, new response fields, new webhook events - ship continuously within v1 and never require you to migrate.

What to expect

New endpoints and fields may appear at any time. Tolerate unrecognized response fields rather than failing on them.
Existing v1 operations and documented success status codes are not removed, and existing writes do not gain new required parameters, request bodies, or JSON properties.
The SDK operation mapping and curated MCP tools are checked against the current contract in CI, so their routes and required scopes cannot silently drift.

Tracking changes

The API Reference always reflects the currently shipped contract - diff it against your integration when you upgrade.
Breaking changes are governed by the Migration and Versioning Policy, which defines the review, notice, and migration path they require.

Changelog

What to expect

New endpoints and fields may appear at any time. Tolerate unrecognized response fields rather than failing on them.
Existing v1 operations and documented success status codes are not removed, and existing writes do not gain new required parameters, request bodies, or JSON properties.
The SDK operation mapping and curated MCP tools are checked against the current contract in CI, so their routes and required scopes cannot silently drift.

Tracking changes

The API Reference always reflects the currently shipped contract - diff it against your integration when you upgrade.
Breaking changes are governed by the Migration and Versioning Policy, which defines the review, notice, and migration path they require.