You need the Mindbody API when another system must read or update studio data directly. Direct use means a developer account, an API key, your approval to activate the site, and whatever fees and call limits Mindbody currently sets. If you only need that data in another business app, a ready-made connection is usually less work than building and maintaining your own.
What is the Mindbody API?
An API lets one piece of software request data from another, or send an update back. Mindbody’s Public API, documented as v6 on the developer portal, lets approved software work with studio data. Common areas include clients, classes, appointments, sales, and memberships. Some calls can write data too, such as booking a client into a class, when that endpoint and your site permissions allow it.
You do not need the API to run the studio inside Mindbody. It matters when another system must use that data: a shop, an email tool, accounting software, or a report Mindbody does not build for you.
The reference is the Mindbody developer portal at developers.mindbodyonline.com. Use that site for endpoints, permissions, fees, and limits. This page explains the process. It does not quote Mindbody’s current prices.
What does it take to get API access?
Direct access has several steps. The developer cannot complete the ones that belong to you.
- A developer account. The person or company building the integration signs up on the Mindbody developer portal and receives an API key.
- A test environment. Work starts on Mindbody’s sandbox data, not your live clients and sales.
- Site activation. To use your real site, you approve the app. The developer sends an activation link or code. You confirm it while logged in as the account owner.
- Authentication on each request. Calls include the API key and your site ID. Calls that act as staff also need a user token tied to a Mindbody staff login.
- Upkeep. Someone has to watch the integration when permissions, staff logins, or API behavior change.
If a developer says they only need an API key, you still have to activate the site. Only the account owner can approve access to studio data.
How much does the Mindbody API cost, and what are the limits?
Mindbody sets API pricing and limits, and both have changed. Do not budget from an old article, including this one. Before anyone writes code, get current answers from the developer portal or Mindbody support.
| Question | Why it matters |
|---|---|
| Is API access included on your plan, or billed separately? | Know whether the studio, the developer, or both may be charged. |
| Are calls metered, capped, or both? | Reading every client several times a day uses far more calls than a daily summary. |
| Are there rate limits? | Large jobs can be slowed or rejected if they request too much at once. |
| Which data needs extra permission? | Some calls depend on site setup and on the staff login used for the token. |
| Who supports API issues? | You want a contact for API problems, not only general product support. |
Record the answers before work starts. A build can look cheap until call volume and Mindbody’s terms show up later.
What do you do today without the API?
Most studios start in Mindbody’s Reports area. Export the view you need, such as sales, attendance or visits, memberships, new clients, or retail. Save the file and move the figures into the other system by hand.
That works for a one-off question. It is a weak habit if the same file is due every week.
Booker is a different product. Use Booker’s reports and exports. If you want software access, ask Booker about its own developer process. A Mindbody API key does not cover Booker.
Where the manual way breaks
- It repeats. Someone exports, cleans, pastes, and checks. The task does not get shorter because you did it last week.
- It waits on one person. If they are away, the books or the contact list wait too.
- The file is already old. It matches Mindbody only at export time. A sale or a new client after that is missing.
- Two systems drift. If you also sell in another shop tool, updating both by hand leads to different stock and sales figures.
- A custom script only delays the problem. It removes the export once. When a login, permission, or endpoint changes, someone must fix it. If that developer leaves, the next person may not know how it works.
Build it yourself or use a connector?
| Build on the API | Use a ready-made connection | |
|---|---|---|
| Who does the work | A developer you hire or employ | The connector handles the technical connection |
| Setup | Developer account, API key, site activation, code, and tests | Connect the apps and describe the outcome |
| Upkeep | You own the fixes | You depend on the vendor to keep the connection available |
| Fits | A need no packaged connection covers | Ordinary jobs, such as sales or clients into accounting, email, or a spreadsheet |
| Risk | One person holds the knowledge | You depend on that vendor |
Choose a direct build when you have a developer and a need no one already connects. For many studios, gyms, salons, and spas, the job is ordinary: sales into the books, new clients into a CRM, or a daily list in a spreadsheet.
How the automated way works with Pandaflow
Pandaflow connects Mindbody to the other apps you use. You keep running the studio in Mindbody. You do not write code for the connection.
- Start free. Create a Pandaflow account. It is free to start.
- Connect your apps. Link Mindbody and the other app in the flow. You still approve access to your Mindbody site.
- Describe the outcome in plain language. For example, send a daily sales summary to accounting, or add new clients to your CRM with the class they booked.
- Review. Check a few real records before you rely on the flow. A small test sale is a useful check if retail is involved.
- Go live. After you approve it, that outcome keeps running.
You are not handling API keys, paging, or retries yourself.
Paid plans are Lite $79, Silver $299, and Gold $499 a month. See pricing for what each plan includes. You can deploy in our cloud or yours.
A connector does not change Mindbody’s terms. If API fees or limits apply on Mindbody’s side, ask Mindbody what they are for your site.
What should you ask a developer?
If you choose a direct build, ask these before any work starts:
- Which Mindbody endpoints will you call, and what data does each one move?
- Who owns the developer account and the API key, the studio or the developer?
- What are Mindbody’s current fees and call limits for this use, and who pays?
- How often will it run, and roughly how many calls does that use?
- What happens when it fails? Who is told, and how is it fixed?
- Where are the code and notes kept, and can someone else take over?
- How do we revoke access if we stop working together?
Plain answers mean the developer has scoped the job. Vague answers mean the cost and the handover risk are still unknown.
What can go wrong
- The key lives in the developer’s account. If they leave, the integration may leave with them. Prefer access you can see and revoke.
- The site was never activated. Sandbox tests can look fine while live data never moves. Approve the site yourself.
- A personal staff login holds the token. If that person leaves or changes a password, calls can stop. Use a dedicated staff login where Mindbody allows it.
- The job copies everything, often. That spends call allowance quickly. Ask whether it can send changes instead of full copies.
- Nobody compares the result. Each month, match a few totals, especially sales, against Mindbody.
For related walkthroughs, see all guides.