ZenotiHelp

Integration framework & infrastructure

ZTZenoti Docs Team Updated April 20, 2026 3 min readGuide

The Zenoti integration framework is the shared plumbing that connects Zenoti to third-party systems β€” authentication, sync scheduling, health monitoring, and retry behaviour. This reference article describes the framework's concepts. For a specific provider's setup, follow its dedicated setup article.


On this page


Integration types

Zenoti integrations fall into the following categories:

  • Payment processors β€” real-time card processing via V1 (center-level) and V2 (organization-level) configurations.
  • Accounting β€” batch financial data sync to Xero, QuickBooks Online, or Codat.
  • E-commerce β€” order and product sync with Shopify.
  • Inventory β€” catalog and purchase order integration with suppliers.
  • PMS β€” real-time folio posting to Oracle Opera (HTNG on-premise and Cloud).
  • Payroll and tips β€” employee data export to ADP Run; tips disbursement via ADP Wisely or MyZen Tips.
  • Fitness networks β€” class reservation sync with ClassPass, BILT, Gympass, FitReserve, Gantner.
  • Communication β€” automated messaging via WhatsApp Business and Zoom.
  • Regional compliance β€” fiscal invoicing for Spain, Saudi Arabia, Montenegro, Malaysia.
  • Club / CSI β€” bidirectional member synchronization with CSI Software.
  • LMS β€” Zenoti University / Northpass learning management.
  • API and automation β€” Zenoti API applications, webhooks, Zapier, SFTP.

Deployment models

Different integrations rely on different deployment models on the external-system side. Always confirm the applicable model before configuring a new integration.

Model Where the external system runs Examples
Cloud (provider-hosted) External system hosted by the provider; Zenoti calls public APIs over HTTPS. Zoom, WhatsApp Cloud API, Northpass, ADP Run, Opera Cloud.
On-premise (customer-hosted) External system runs at the customer's site, typically with a vendor-supplied bridge or connector. Opera HTNG, some CSI Software deployments.
Hybrid Mixed β€” some endpoints provider-hosted, others customer-hosted. Some multi-property hotel PMS configurations.

Obsolete terms (for example, "on-premise cloud") should not be used β€” classify each integration as cloud or on-premise based on where the external system physically runs.


Authentication models

Integration Authentication
Xero OAuth 1.0a
QuickBooks Online OAuth 2.0
Shopify OAuth 2.0
Zoom OAuth 2.0
WhatsApp Business Meta embedded signup (WABA)
ZATCA x-api-key
Fiskaly Bearer token
Montenegro DDDI IoT Authorization header
ADP Run Multi-token OAuth
ADP Wisely / MyZen Tips Program credentials
Stripe Connect OAuth 2.0
Adyen, V2 processors API key
V1 processors Merchant credentials (ID, key, password)
Opera HTNG HTNG service account (basic auth)
Opera Cloud OAuth (password or client_credentials) + AppKey header
CSI Software Provider-issued API key or service credential
Northpass (Zenoti University) API key
API applications API key generated by Zenoti
Webhooks HTTPS endpoint with optional signature

Integration health monitoring

Zenoti provides an integration health dashboard that shows the real-time status of every active integration. See Monitor integration health and metrics.


Integration pause scheduling

Pause scheduling temporarily suspends batch/scheduled sync activity without removing credentials. See Integration pause scheduling.


Retry and error handling

Batch integrations (accounting, payroll, inventory, tips, CSI):

  • Failed records are automatically retried in the next sync cycle.
  • Persistent failures are flagged in the sync log with error details.
  • You can manually retry individual records or date ranges from the integration page.

Real-time integrations (payments, PMS, fiscal invoicing):

  • Errors surface immediately in the UI.
  • Retry is available from the invoice or transaction record.
  • Failed real-time calls never roll back the underlying Zenoti action β€” the user takes the next step manually.

Settings inheritance

Integration settings inherit from organization to center: center-level settings override organization-level settings. If a center has no integration-specific configuration, organization-level settings apply. Always confirm the effective level before changing a value.


Network posture

All Zenoti integrations use outbound HTTPS (port 443). Plain HTTP is not supported.

For integrations where the external system initiates connections to Zenoti (Opera reservation notifications, some CSI deployments), the external system must be able to reach a Zenoti-managed URL over outbound HTTPS. Provider-specific endpoints are documented in the corresponding setup article; treat any endpoint path shown in an article as an implementation detail to whitelist, not as configuration you must type.


Tips

  • When configuring a new integration, start from its dedicated setup article β€” this reference is background only.
  • When diagnosing cross-integration issues, start at the shared layer (health dashboard, pause schedules, network posture) before digging into a single provider.
  • Document which centers use which integrations so that configuration changes and pause windows can be reviewed with the right stakeholders.

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