MINDBODY connector icon

MINDBODY Connector

Build embedded automations that sync MINDBODY client records, class schedules, bookings, purchases and memberships into your SaaS. Create customer-facing flows that create or update clients, post bookings, update enrollments and push purchase data to CRMs, calendars or accounting systems.

Build with this Connector Talk to an integration expert
01

Native in-app delivery

Deliver integrations directly inside your product UI for end users.

02

Reusable templates

Create once, reuse workflows across customer accounts and products.

03

Webhook-driven automations

React to booking events to trigger real-time flows and actions.

04

Embedded experience

Deliver customer-facing workflows natively inside your SaaS product.

CONNECTOR OVERVIEW

What you can integrate or automate with MINDBODY

Teams can sync MINDBODY clients, bookings, class schedules, purchases, memberships and location data into their product and automate downstream actions. Use Cyclr to combine MINDBODY methods, respond to booking webhooks and orchestrate multi-step flows — see the MINDBODY developer portal for API details. Mindbody developer portal.

PRODUCT USE CASES

Top Use Cases for MINDBODY Integrations

Automate common studio and wellness workflows for every customer account. Use MINDBODY triggers and actions to create clients, sync bookings and class enrollments, push purchases to finance systems, and notify staff or downstream apps when memberships change.

Create or update CRM contact from new MINDBODY client

When MINDBODY adds a client (List New Clients/Add Client), create or update a contact in CRM and map membership details.

Notify staff and update calendars on booking creation

Respond to Client Booking Created webhook to create calendar events, alert staff, and update booking records in your app.

Push purchases to accounting when members buy packages

On List New Client Purchases or Purchase events, create invoices or payment entries in your accounting system.

ORCHESTRATION

How MINDBODY works with Cyclr

Cyclr sits between your SaaS product and MINDBODY 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

    MINDBODY

    MINDBODY 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 MINDBODY methods you can orchestrate through Cyclr.

Client12

List Client Account Balances

Action

Gets client account balances.

List Client Contract

Action

Gets collection containing all of the clients contracts.

List Client Indexes

Action

Client indexes are used to analyze client demographics. A business owner can set up different categories with sets of values which they can assign to each client. Client indexes are used in client searches, for tagging clients so that the owner can send mass emails to similar groups, and for many reports.

List Client Purchases

Action

Gets a list of purchases made by a specific client.

List Updated Client Visits

Action

Gets collection containing the updated clients visits since the last run.

List New Client Purchases

Action

Gets a list of new purchases made by a specific client since last run.

List Updated Contact Logs

Action

Gets not just all contact logs, but also system-generated contact logs, contact logs assigned to specific staff members, and contact logs of specific types or subtypes since the last run.

List Client Visits

Action

Gets collection containing the clients visits.

Get Client By Client ID

Action

Get a client using their unique ID.

List Cross Regional Client Associations

Action

Returns a list of sites that a particular client ID (also referred to as an RSSID) or a client email address is associated with in a cross-regional organization. Either the ClientID or Email parameter is required. If both are provided, the ClientID is used.

List Updated Client Account Balances

Action

Gets updated client account balances since the last run.

List Contact Logs

Action

Gets not just all contact logs, but also system-generated contact logs, contact logs assigned to specific staff members, and contact logs of specific types or subtypes.

Client Lookup4

List Client Referral Types

Action

Gets a list of referral types. Referral types are options that new clients can choose to identify how they learned about the business. Referral types are typically used for the sign-up process.

List Custom Client Fields

Action

Gets collection containing custom fields.

List Client Services

Action

Gets the purchased services for a specific client.

List Required Client Fields

Action

Gets collection containing all of the clients required fields.

Appointments3

List Appointment Options

Action

List the appointment options.

List Staff Appointments

Action

Returns a list of appointments by staff member.

List Active Session Times

Action

Returns a list of the times that can be booked for a given program schedule type. ActiveSessionTimes represent the scheduling increments that can be booked during the active business hours for services

Enrollments2

List Enrollments

Action

Gets collection containing all of the clients

List Updated Enrollments

Action

Gets collection containing all of the updated enrollments since last run.

Sales5

List New Sales

Action

Gets collection of sales since last run.

List Sales

Action

Gets collection of sales.

List Products

Action

Gets collection of products.

List Services

Action

Gets collection of services.

List Packages

Action

Gets collection of packages.

Classes5

List Updated/New Classes Schedules

Action

Gets all enrollments that occur since last run.

List Classes

Action

Gets list of classes.

List Class Descriptions

Action

Gets list of class descriptions.

List Updated Classes

Action

Gets list of classes.

List Classes Schedules

Action

Gets list of class schedules.

Activation2

Get Activation Code

Action

Call to retrieve a site-specific activation code.

User Token

Action

Clients5

List Updated Clients

Action

Gets collection containing all of the clients updated since last run.

List New Clients

Action

List all clients added since last run.

Search Clients

Action

Gets collection the clients matching there search text.

List Clients

Action

Gets collection containing all of the clients

Add Client

Action

Adds a client.

Site6

List Locations

Action

Get list locations.

List Resources

Action

Get list of resources.

List Sites

Action

Get list of sites..

List Session Types

Action

Get list of session types.

List Programs

Action

Get list programs.

List New Resources

Action

Get list of all new resources since last run.

Memberships1

List Active Client Memberships

Action

Gets all active client memberships.

Webhooks1

Client Booking Created

Webhook

Sends this event when a client is booked into a class.

TECHNICAL DETAILS

MINDBODY integration and API details

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

API and authentication

API host
https://api.mindbodyonline.com/public/v6
Authentication
API key; OAuth 2.0
Credentials

SiteId; API-Key; staff username and password (for token flows); optional OAuth client id and secret.

Method categories

Clients; Classes; Bookings; Purchases; Memberships; Site metadata; Activation; Webhooks

View vendor API documentation →

Pagination and rate limits

Pagination

Many endpoints use pageNumber pagination; responses include pageCount for total pages.

Rate limits

Rate limits vary by endpoint and are assigned per API key; contact Mindbody Developer Support for exact limits.

IMPLEMENTATION

Authentication at a glance

MINDBODY supports API-Key header authentication and OAuth 2.0 staff/consumer tokens. Cyclr’s connector requires API key, Site ID and staff credentials to obtain user tokens; confirm available flows in Cyclr Console.

Authentication method
API key; OAuth 2.0
Credential required

SiteId; API-Key; staff username and password (for token flows); optional OAuth client id and secret.

Before you begin:

Requires a Mindbody developer account and Mindbody approval to go live; sandbox available.

View setup guide

COMMON QUESTIONS

Frequently asked questions

It synchronizes MINDBODY clients, bookings, class schedules, purchases, memberships and locations, and can trigger downstream flows like CRM updates, calendar events and accounting entries.

MINDBODY requires an API-Key header and supports OAuth 2.0 tokens; the Cyclr connector asks for API key, SiteId and staff credentials (used to obtain tokens) during setup.

Yes. Cyclr’s multi-tenant architecture isolates customer accounts so you can publish the same integration templates across customers while keeping credentials and data segregated.

Yes. Cyclr lets you expose approved connector methods and templates as governed MCP workflow tools with tenant scoping, audit trails and access controls.

KEEP EXPLORING

Related resources and connectors

Documentation

CRM Integrations you should be using

Read more →Product

What is iPaaS?

Read more →Product

MCP PaaS

Read more →Related connector

Aesthetic Record

Related Crms connector for customer-facing integration workflows.

Related connector

Booker

Related Crms connector for customer-facing integration workflows.

Related connector

Club Ready

Related Crms connector for customer-facing integration workflows.

Let Cyclr handle the integrations.

You focus on building the product your customers love.

Start building for free Get a demo