Booker connector icon

Booker Connector

Embed Booker booking and client workflows directly in your SaaS product. Build two-way automations to create appointments, manage client records, sync staff availability and service menus, and orchestrate confirmations and payments inside your app.

01

Two-way appointment sync

Create and update Booker appointments from your app.

02

Unified client profiles

Provision and reconcile client records across systems.

03

Real-time availability

Surface staff schedules and service availability instantly.

04

Embedded experience

Deliver customer-facing workflows natively inside your SaaS product.

CONNECTOR OVERVIEW

Overview

Integrate Booker to sync appointments, client records, staff schedules, service menus and payments between your app and Booker. Using Cyclr’s low-code builder you can create two-way booking flows that create appointments and client records, keep availability current, and trigger confirmations, refunds or marketing actions across connected systems.

PRODUCT USE CASES

Top Use Cases for Booker Integrations

Quickly create integrations between your SaaS application and Booker with Cyclr’s low-code integration builder. Publish your Booker integration into your application using Cyclr’s white-label embedded integration marketplace.

In-app booking and calendar sync

Create appointments in Booker from your app, push confirmations and keep calendars synchronized.

Client provisioning and profile sync

Create and update Booker client records and keep contact and visit history in sync.

Staff availability and service menus

Pull staff schedules and service offerings to display accurate availability and durations.

ORCHESTRATION

How Booker works with Cyclr

Cyclr sits between your SaaS product and Booker to handle authentication, govern access and orchestrate every API call per customer, at scale.

  1. 1

    Your SaaS product

    Your app requests an action for a specific customer.

  2. 2

    Cyclr orchestration

    Cyclr authenticates, applies policies and routes the request.

  3. 3

    Booker

    Booker processes the request and returns a response to your app.

Customer-specific authentication · Governed data movement · Centralized visibility and audit

CONNECTOR COVERAGE

Available connector capabilities

Explore Booker methods you can orchestrate through Cyclr.

Orders4

Get Order

Action

Get an order by ID.

List Orders

Action

Get a list of all orders.

List New Orders

Action

Get a list of all orders created since last run.

List Updated Orders

Action

Get a list of all orders updated since last run.

Customers5

Get Customer

Action

Get a list of customers by ID.

List Customers

Action

Get a list of all customers.

List New Customers

Action

Get a list of all customers created since lastrun.

List Updated Customers

Action

Get a list of all modified customers since lastrun.

Find Customer(s)

Action

Get a list of all customers matching search criteria.

Locations2

List All Locations

Action

Get a list of all locations.

Find Location

Action

Get a location.

TECHNICAL DETAILS

Booker integration and API details

Review the sourced authentication and API behaviour used when configuring customer-facing Booker integrations in Cyclr.

API and authentication

API host
https://api.mindbodyonline.com/public/v6
Authentication
Developer app registration with API key, SiteId and token; OAuth 2.0 supported for delegated flows
Credentials

Developer account, API key or OAuth client ID/secret, SiteId, redirect URI, optional user credentials for tokens.

Method categories

Appointments, Clients, Services, Staff, Availability, Sales/Payments, Sites, Webhooks.

View vendor API documentation →

Pagination and rate limits

Pagination

Mindbody endpoints return paginated results (Limit and Offset parameters); filter by date ranges to reduce pages or auto-paginate client-side.

Rate limits

Refer to the vendor API documentation for current limits.

IMPLEMENTATION

Authentication at a glance

Booker (via Mindbody developer portal) requires app registration; authentication uses a developer API key and SiteId plus user tokens or OAuth 2.0 for delegated calls.

Authentication method
Developer app registration with API key, SiteId and token; OAuth 2.0 supported for delegated flows
Credential required

Developer account, API key or OAuth client ID/secret, SiteId, redirect URI, optional user credentials for tokens.

Before you begin:

Developer app registration and live-access approval required; SiteId and per-site permissions needed.

View setup guide

COMMON QUESTIONS

Frequently asked questions

It synchronizes appointments, client records, staff schedules, service menus and sales so your product can create bookings, update clients and reflect availability in real time.

Booker integrations require a Mindbody developer account and app registration; authentication uses a developer API key and SiteId plus optional user tokens or OAuth 2.0 for delegated operations.

Yes. Cyclr supports multi-tenant orchestration: reuse the same integration logic while supplying each customer’s SiteId and credentials to keep data separate.

Yes. Cyclr lets you expose approved Booker methods as governed MCP tools with tenant-aware controls and standardized orchestration for product teams.