Picking a version
Every request resolves to exactly one version, in this order:- The
Clemta-Versionheader, if you send one. - Your account default, pinned the first time you created a key.
- The latest version, if neither of the above applies.
What a version pins
A dated version pins the request and response shapes and the set of error codes. When a new version renames or restructures a field, the old version still answers with the old shape. Your integration does not have to move until you choose to. An unknown version is rejected withinvalid_api_version. Use a date the
API versions page lists, or omit the header to run on your
account default.
Deprecation and sunset
A version can be deprecated once a newer one supersedes it. It keeps answering until a published sunset date, but every response on it carries two headers:Deprecationmarks the version as deprecated.Sunsetis the date after which it may stop answering.
Webhooks are versioned too
The events we deliver to your endpoint are versioned the same way. Each delivery is rendered at the webhook version set for your workspace, so a payload keeps its shape even as newer API versions restructure the same resource. The event’sdata.object therefore matches the version you integrated against, not
necessarily the latest one. Set your webhook version in the dashboard. It
defaults to the API version pinned on your account.