ZenotiHelp

Zenoti APIs overview

ZTZenoti Docs Team Updated May 12, 2026 4 min readGuide

Zenoti provides a comprehensive set of REST APIs that allow you to integrate external applications with your Zenoti organization. You can use these APIs to automate operations, synchronize data with third-party systems, and build custom workflows for service booking, product sales, membership management, gift card processing, and more.


Before you deploy

Verify the following before integrating against the Zenoti REST APIs.

Prerequisite Why it matters
Developer access to your Zenoti organization API keys and OAuth client credentials are scoped to a single organization; you need access to generate them from Admin > Organization > API.
API key (for server-to-server) or OAuth client credentials (for access-token flows) API keys provide organization-wide access; access tokens provide role-scoped access. Choose based on whether the caller needs role-based restrictions.
Awareness of the default rate limit (60 calls per minute per organization) Exceeding the limit returns 429 Too Many Requests. Plan retry-with-backoff and pagination strategies before going live.
A registered webhook destination URL with TLS (for webhook-driven integrations) Webhooks require an HTTPS endpoint that can accept POSTs and respond within Zenoti's delivery window.

For step-by-step setup, see Set up API authentication and Get started with Zenoti APIs.


On this page


What you can do with Zenoti APIs

Zenoti APIs cover the core operational areas of the Zenoti platform:

  • Service booking -- Create, reschedule, and cancel appointments. Reserve time slots, confirm bookings, and collect payment through a complete booking workflow.
  • Product sales -- Retrieve product catalogs, generate invoices, and process payments for retail product sales.
  • Membership management -- List available memberships, sell memberships to guests, and manage membership lifecycle operations including freeze, unfreeze, cancel, and reinstate.
  • Gift card processing -- Create gift card templates, generate sale invoices, process payments, and send confirmation emails to recipients.
  • Guest management -- Create and update guest profiles, manage saved payment methods, track loyalty points, and merge duplicate guest records.
  • Employee management -- Add employees, manage schedules, track attendance, and configure blockout times.
  • Reporting -- Access operational reports for revenue, appointments, inventory, and other business metrics.

How Zenoti APIs work

Zenoti APIs follow REST conventions and use standard HTTP methods:

  • GET -- Retrieve data (centers, guests, services, appointments)
  • POST -- Create new records or perform actions (create a booking, generate an invoice)
  • PUT -- Update existing records (update guest details, reschedule an appointment)
  • DELETE -- Remove records (revoke tokens, delete saved cards)

All API requests are made to the base URL https://api.zenoti.com and all responses are returned in JSON format. Successful responses include the requested data, while errors return a JSON object with an error key containing a code and description.

Authentication methods

Zenoti supports two authentication methods:

Method Use case Header format
API key Server-to-server integrations that access organization-wide data Authorization: apikey {{api_key}}
Access token Client-side applications that need role-based access control Authorization: bearer {{access_token}}

API keys do not expire but provide unrestricted access scope. Access tokens expire after a set period and provide role-based access that respects the user's security permissions. For most integrations, Zenoti recommends using access tokens for tighter security control.

For detailed setup instructions, see Set up API authentication.

API domains

The Zenoti API is organized into domains that map to functional areas of the platform:

Domain Description
Authentication Generate, refresh, and revoke access tokens
Centers Retrieve center details, categories, rooms, employees, services, packages, products, and memberships at the center level
Guests Create and manage guest profiles, notes, forms, saved cards, memberships, loyalty points, and relationships
Employees Add and manage employees, schedules, attendance, blockout times, and security roles
Service booking Create bookings, check available slots, reserve slots, confirm bookings, and manage appointment lifecycle
Appointments List, retrieve, check in, check out, complete, and cancel appointments
Invoices Create and manage invoices for services, products, memberships, packages, and gift cards; process payments
Gift cards Manage gift card templates, check balances, and process gift card sales
Opportunities Create and manage sales leads and opportunity notes
Classes Register for classes, manage class schedules and bookings, and retrieve class metrics
Organizations Retrieve organization-level configuration and settings
Reports Access operational and financial reports
Inventory and vendors Track inventory levels and manage vendor records
Queue Manage the guest queue at centers
Webhook events Subscribe to real-time event notifications for guest, invoice, appointment, membership, and other entity changes
Integrations Connect with Shopify, ePrescribe, and digital forms

Webhooks

Webhooks deliver real-time notifications to your application when events occur in Zenoti. Instead of polling the API for changes, you register a destination URL and Zenoti sends an HTTP POST request with event data whenever a subscribed event occurs.

Supported event categories include guest lifecycle events, invoice closure, appointment status changes, membership operations, class bookings, package redemptions, and employee changes.

For webhook setup and configuration, see Set up webhook integration.

Rate limits and pagination

Zenoti enforces a default rate limit of 60 API calls per minute per organization. Response headers indicate your remaining quota and reset time. For strategies to work within rate limits, see Configure API rate limits.

All list endpoints support pagination with page and size query parameters. The maximum page size is 100 records per request. For pagination implementation details, see Configure API pagination.

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