Versions and changes
The API’s version is in the address: /api/v1/external. Events also say which version made them, in api_version (today 2026-10-01).
What we may add at any time
Section titled “What we may add at any time”These don’t break a well-written integration, so we add them without notice:
- New endpoints.
- New fields in replies and events.
- New event types (you only get the ones you ask for).
- New error codes, outcome words, statuses and
reasonvalues. - New optional fields in requests.
So: ignore fields you don’t know, and have a sensible default for a code or word you haven’t seen.
What we never change without notice
Section titled “What we never change without notice”Renaming or removing a field, an endpoint, an error code, an outcome word or an event type. That gets at least 6 months’ notice, and the old way keeps working until then.
An endpoint on its way out answers with a Deprecation: true header, and the reference marks it as old. For example, the first webhook endpoints (/webhooks) still work, but point you to /webhook_endpoints with a Link header.
We plan to add dated versions you can pin, sent as a CallView-Version header, so you can move to a new version when it suits you. Until then there is one version, and the rules above apply.