← Back to all docs

MINDBODY API

MINDBODY is a business management platform for fitness, wellness, and beauty businesses, combining scheduling, payments, client management, marketing, and reporting in one system. An unofficial API lets you programmatically pull classes, appointments, clients, sales, and staff data—and push updates like new bookings, client records, and class registrations back into MINDBODY without wrestling with site-by-site source credential activation.

By Alex KlarfeldMay 29, 2026
MINDBODY API

What is MINDBODY?

MINDBODY is a business management platform that combines scheduling, payments, client management, and marketing tools for fitness, wellness, and beauty businesses. Studios and salons use MINDBODY to schedule classes and appointments, process payments and point-of-sale, manage client relationships, run marketing automation, and report across single or multi-location operations—reaching consumers through branded mobile and web apps and the ClassPass network.

Core product areas include:

  • Scheduling & Operations (class/appointment scheduling, staff management, substitution automation)
  • Payments & Transactions (payment processing, point-of-sale, retail product management)
  • Client Experience (branded mobile app, branded web tools, Messenger[ai] communication)
  • Marketing & Growth (marketing automation, lead management, ClassPass integration)
  • Reporting & Analytics (business dashboards, performance metrics, customizable reports)
  • Multi-location Management (corporate-level controls, centralized staff management, network reporting)

Common data entities:

  • Sites, Locations, Staff, Resources
  • Classes, Class Schedules, Enrollments, Waitlists
  • Appointments, Appointment Types, Availabilities
  • Clients, Memberships, Contracts, Account Balances
  • Sales, Products, Services, Packages, Gift Cards

The MINDBODY Integration Challenge

Studios run their daily operations on MINDBODY, but turning that into reliable API-driven automation is non-trivial:

  • Source credential gating: The Public API requires developer source credentials plus a per-site activation code, so onboarding each studio location is a manual approval step
  • Per-site fan-out: Multi-location brands and franchises expose a separate site ID per location, multiplying credentials, tokens, and reconciliation work
  • User vs. staff tokens: Booking and account actions require a user token in addition to API credentials, complicating headless automation
  • Mobile-first client data: Much of the client experience lives in branded apps, so some workflows are only reachable through authenticated app surfaces
  • Rate and pagination limits: Large class schedules and client lists must be paged and throttled to stay within Public API constraints
  • Payments and POS sensitivity: Sales, contracts, and retail transactions demand careful idempotency and reconciliation against the studio's point-of-sale

How Supergood Creates MINDBODY APIs

Supergood reverse-engineers MINDBODY's Public API and authenticated app flows to deliver a resilient API layer for your sites—handling source credentials, per-site activation, and user tokens so you integrate once across every location.

  • Manages source credentials, site activation codes, and user tokens securely in a managed session
  • Maintains session continuity with automatic token refresh and change detection
  • Normalizes responses across Classes, Appointments, Clients, Sales, and Staff so you integrate once and rely on consistent objects
  • Fans out across multiple site IDs for multi-location brands while presenting a single unified surface

Use MINDBODY with AI agents: MINDBODY MCP Server →

Getting Started

  • Schedule Integration Assessment

Book a 30-minute session to confirm your sites, locations, and authentication model.

  • Supergood Generates and Validates Your API

We deliver a production-ready MINDBODY adapter tailored to your sites and entitlements.

  • Deploy with Monitoring

Go live with continuous monitoring and automatic adjustments as MINDBODY evolves.

mindbody

API Endpoints

Authentication

POST/authenticate

Authenticate with source credentials and a site activation code, and obtain a user/session token for downstream calls.

Classes

GET/classes

List classes and class schedules for a site with filters for program, location, staff, and date range.

Classes

POST/add_client_to_class

Enroll a client into a class or add them to a waitlist against the studio's schedule.

Appointments

GET/appointments

Retrieve appointments, appointment types, and staff availabilities with status and date filters.

Clients

GET/clients

Pull client records, memberships, contracts, and account balances across one or more sites.

Clients

POST/create_client

Create or update a client profile with contact details, membership, and consent flags.

Sales

GET/sales

Retrieve sales, products, services, packages, and gift card transactions from the point-of-sale.

Use Cases

Sync class and appointment schedules across locations

- Pull class schedules, enrollments, and waitlists from every site into a single source of truth - Stream appointment and availability changes to downstream booking and CRM tools - Reconcile staff assignments and substitutions without portal clicks

Unify client and membership data

- Sync client profiles, memberships, and contracts across multi-location brands - Push new client records and consent updates back into MINDBODY - Surface account balances and membership status to retention workflows

Reconcile sales and point-of-sale revenue

- Sync sales, products, packages, and gift card transactions into accounting and BI systems - Match retail and service revenue against payouts and reporting dashboards - Flag refunds, voids, and failed payments to finance workflows

Automate booking and registration workflows

- Enroll clients into classes and appointments from your own app or website - Trigger marketing and lead nurture when a client books or cancels - Keep ClassPass and partner availability in sync with the studio schedule

Technical Specifications

Authentication

Developer source credentials plus per-site activation codes and user tokens, handled in a managed session

Connectivity

MINDBODY Public API V6.0 (https://api.mindbodyonline.com/public/v6) plus authenticated app flows where the public API does not reach

Response format

Normalized JSON across Classes, Appointments, Clients, Sales, and Staff objects

Rate limits

Adaptive throttling and pagination tuned to your sites to avoid Public API limits

Session management

Automatic user-token refresh, site activation handling, and credential rotation

Data freshness

Near real-time pulls for schedules, clients, and sales with optional scheduled batch syncs

Security

Encrypted credential vault, scoped access tokens, SOC 2-aligned controls, and audit logging

Webhooks

Event-style callbacks for class enrollment, appointment changes, client updates, and sales

Latency

Sub-second reads on cached entities; multi-second writes when posting bookings and sales

Throughput

Horizontally scaled workers sized to multi-location class and client volume

Reliability

Retry, backoff, and idempotency keys for bookings, registrations, and sales transactions

Adaptation

Continuous monitoring of MINDBODY Public API releases and per-site configuration drift

Frequently asked questions

Supergood works with your authenticated MINDBODY access. We handle the source credential and per-site activation flow on your behalf, so you do not have to manage individual site tokens yourself.

Yes. Multi-location brands and franchises expose a separate site ID per location, and Supergood fans out across them while presenting a single unified, normalized API surface.

Yes. You can pull classes, appointments, clients, and sales, and push updates such as new bookings, client records, and class enrollments back into MINDBODY.

Supergood builds on the Public API where it is available and supplements it with authenticated app flows for workflows the public API does not expose, then normalizes everything into one consistent schema.

Supergood applies idempotency keys, retries, and backoff to bookings, registrations, and point-of-sale transactions so duplicate or partial writes are avoided during reconciliation.

Ready to get a real API?