ZenotiHelp

API changes

ZTZenoti Docs Team Updated May 12, 2026 1 min readGuide

API-level breaking changes — endpoint behavior changes, request or response schema deltas, deprecated routes — have their own changelog separate from the all-edition release notes.

Note: The API changelog is maintained alongside the API reference, where each entry documents the API endpoint, scenario, earlier behavior, new behavior, and a link to the relevant API documentation.

On this page

Where to find the API changelog

The API changelog lives under the Zenoti APIs category in the Releases section. It documents every API-level change going back to August 2021.

Learn more: Zenoti APIs releases

What is documented

Each API changelog entry typically captures:

  • API endpoint or webhook event — the affected route or event name
  • Scenario — the situation in which the change applies
  • Earlier behavior — what the API did before the change
  • New behavior — what the API does now
  • API documentation link — pointer to the up-to-date endpoint reference

How API changes relate to release notes

When an API change is shipped, it appears in two places:

  1. The all-edition release notes for that release date, under Announcements or as a > **Breaking change:** admonition with a **Learn more:** link pointing here.
  2. The Zenoti APIs Releases section, with the full structured entry — endpoint, scenario, earlier vs. new behavior.

If you integrate with Zenoti APIs or maintain a Redshift / S3 data pipeline against the analytics data sources, subscribe to or periodically review the API changelog in addition to the release notes.

Was this article helpful?
Your feedback helps us improve our documentation.