Changelog

By API and contract

Each page below is generated at build time from the CHANGELOG.md that the service keeps in its own repository (main branch). Only what touches the public contract is included; the full record stays in the repository.

Content APIcanverly-api

Sites & organizationscanverly-tenancy

Formscanverly-forms

Event contractscanverly-contracts

The current version of each specification is shown at the top of its page under OpenAPI by service.

Versioning policy

• The API version is in the URL prefix (/v1, /v2, …). A breaking change ships as a new prefix version; the current one stays up.
• An additive change (new optional field, new endpoint, new enum member) ships without prior notice and without changing the prefix. Write your client to ignore fields it does not know.
• N-1 support: when a new prefix version is released, the immediately previous version remains supported. Today only /v1 exists.

Still to be decided

To be decided

These parts of the policy have not been decided yet and therefore have no number here: how long version N-1 stays up after N is released; the minimum notice before a deprecation is announced; and through which channel, besides this page, the notice reaches integrators.

The documentation published since the old docs.canverly.com promises at least 90 days of notice (Interactive reference); that deadline is not recorded as a decision and is still to be confirmed.