API changelog and compatibility

Track the public contract and prepare for reviewed changes.

September 26, 2026: integration contract prepared

This revision defines Business and Enterprise integration eligibility, scoped identity and resource discovery, entry and booking operations, bounded analytics, events, webhook management and dedicated API-key authentication for Zapier.

Publication of documentation does not enable production launch flags, grant a migration entitlement or confirm Zapier directory approval. Account controls and the release notice identify available capabilities.

Preserve existing clients

The public namespace remains /v1/external and existing successful resource envelopes are preserved. Legacy sensitive-field access and non-expiring keys require an explicit migration path; do not infer a breaking cutover from this documentation date.

Additive fields may be compatible, but new enum values still need consumer review. The proposed policy is 90 days’ notice for breaking changes, with explained urgent security exceptions. Any notice includes the affected behavior, migration steps and effective date.