API Deprecation Policy published
The Qmatic Orchestra API Deprecation Policy is now published on the Developer Portal.
The policy sets out how API changes are classified, how deprecations are announced, and what the support timeline looks like for deprecated endpoints — so you can plan integrations with confidence.
Key points
- Backward compatible changes (new optional fields, new endpoints) require no action from integrators.
- Breaking changes always require a deprecation notice first — no silent removals.
- Deprecation window: a deprecated endpoint remains supported through the next minor version and is removed in the one after (e.g. deprecated in v7.1 → removed in v7.3).
- Partner support: access to a shared hosted environment is available during the deprecation window to validate integrations against the new version.
Read the full policy in the Community section.