Source connector

Mindbody connector

Mindbody integration for databases, warehouses and BI tools

Booking and membership platform for wellness studios. Datrise captures Mindbody entities such as clients, class bookings, memberships, staff, sales and appointments, then lands normalized and typed models for warehouse reporting, attribution, and AI workflows.

The Mindbody Public API v6 authenticates with API key, OAuth 2.0, and Mindbody caps calls at 1,000 API calls per day per API key in live mode; overage beyond that is billed at roughly $0.003 per call rather than hard-throttled, on top of separate undocumented per-endpoint "system limits".

Of the 6 objects, 6 sync as upserts keyed on the primary key and 0 as append-only streams, so each incremental run moves only what changed since the last watermark. Every object lands in its own table (for example `mindbody_clients`) with a schema derived from the Mindbody API rather than a flattened CSV, in any of the 43 supported destinations.

Datrise is in early access: pick a destination below to open the Mindbody pipeline page, and join the waitlist to get the Mindbody connector (CRM) with guided onboarding.

Incremental syncSchema-aware mapping43 destinations available

What Mindbody data Datrise extracts

Each object lands in its own typed table. Sync mode is derived from the object: history-style objects append, everything else upserts.

Object	Landing table	Sync mode
clients	mindbody_clients	Upsert by primary key, incremental on updated-at
class bookings	mindbody_class_bookings	Upsert by primary key, incremental on updated-at
memberships	mindbody_memberships	Upsert by primary key, incremental on updated-at
staff	mindbody_staff	Upsert by primary key, incremental on updated-at
sales	mindbody_sales	Upsert by primary key, incremental on updated-at
appointments	mindbody_appointments	Upsert by primary key, incremental on updated-at

Mindbody API: setup facts for the connector

Verified against the vendor documentation on 2026-09-02. Unknown values are left blank rather than guessed.

API	Mindbody Public API v6
Authentication	API key, OAuth 2.0 — Every request needs a static `Api-Key` header plus a `SiteId` header identifying the business; staff- and client-scoped operations additionally require an OAuth 2.0 bearer token issued by the Mindbody Identity Service.
Pagination	offset — List responses return a `PaginationResponse` object (`RequestedLimit`, `RequestedOffset`, `PageSize`, `TotalResults`) rather than a Link header or opaque cursor token.
Rate limit	1,000 API calls per day per API key in live mode; overage beyond that is billed at roughly $0.003 per call rather than hard-throttled, on top of separate undocumented per-endpoint "system limits".
Incremental cursor	Not published
Webhooks	Yes — Mindbody Webhooks subscription API (client.created/updated/deactivated, classSchedule.created/updated/cancelled, clientSale.created, classRosterBooking.created/cancelled, etc.)
Bulk export	No
Deletes detectable	Yes — Records are soft-deleted/deactivated rather than hard-deleted — e.g. a `client.deactivated` or `site.deactivated` webhook event fires instead of a delete, and there is no hard-delete flag documented on the core list endpoints.

Official API reference

What bites when replicating Mindbody

The Public API is metered at 1,000 calls per day per API key in live mode; overage is billed at roughly $0.003 per call rather than hard-throttled.
Every request needs both an `Api-Key` header and a `SiteId` header — a valid OAuth bearer token alone is not sufficient.
List endpoints return pagination state in a `PaginationResponse` body object (`RequestedLimit`, `RequestedOffset`, `PageSize`, `TotalResults`) instead of a Link header, so clients must read the body, not headers, to page.
Webhook deliveries are not guaranteed once or in order, and failed deliveries retry every 15 minutes for up to 3 hours before Mindbody auto-deactivates the subscription.

Compare this against every other documented API

Popular destinations for Mindbody

Choose a destination below to open the ready pipeline page.

A
Airtable
Relational spreadsheet destination for ops and go-to-market teams.
View pipeline
A
Amazon Athena
Serverless SQL over S3 data lake tables.
View pipeline
A
Amazon DynamoDB
Serverless key-value and document store on AWS.
View pipeline
A
Amazon QuickSight
AWS serverless BI with SPICE and embedded analytics.
View pipeline
A
Amazon Redshift
AWS petabyte-scale warehouse with Spectrum.
View pipeline
A
Amazon S3 Data Lake
Object storage landing zone for parquet and snapshots.
View pipeline
A
Apache Superset
Open-source BI for SQL exploration, charts, and dashboard publishing.
View pipeline
A
Azure Data Lake Storage
ADLS Gen2 object storage for analytics workloads.
View pipeline
A
Azure Synapse
Microsoft analytics workspace with SQL pools.
View pipeline

Mindbody connector FAQ

What Mindbody data does the connector extract?: 6 objects: clients, class bookings, memberships, staff, sales and appointments. Each lands in its own table with types preserved; history-style objects (0) load as append-only streams.
Is the Mindbody integration incremental?: Yes. After the initial full load, every run reads only records changed since the last watermark (updated-at or event timestamp) and applies an upsert or an append depending on the object.
Where can I load Mindbody data?: Into 43 destinations: relational databases, cloud warehouses, data lakes, spreadsheets and BI tools. Each Mindbody → destination pair has its own page with the object-to-table mapping.

Related CRM sources

Other sources in the same category, each with its own connector page.

Early access

Launch your Mindbody pipeline with guided onboarding

Join the waitlist to get priority access for Mindbody integrations with guided setup, schema-aware mapping, and production-grade incremental sync.