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.

What's new in v7.4​

Three brand-new APIs join the v7.0 surface:

• OAuth2 — full OAuth 2.0 authorisation, token issuance and client management.
• Personal Data — customer master data, custom fields and retention policies (GDPR-aligned).
• Variables — runtime variable groups for branches and devices.

Plus the existing five — Calendar, Common, Configuration, Mobile, Statistics — bringing the published surface to 453 endpoints across 8 APIs.

Getting started​

Browse the Orchestra 7.4 API reference — every endpoint has parameters, schemas and a Send-API button on the page.

For appointment integrations, the Appointment Integration guide walks through the typical third-party push and customer self-booking flows against real Calendar API endpoints.