A8gent
All articles

Industry

Mindbody API Cost: What a Studio Actually Pays for an Integration

Mindbody charges the developer account, not the studio's subscription, for API use: $0.002 per call on its current pricing card, with free access under 5,000 calls per billing cycle. Here is how the fee works, the Site ID rule that bills every location, how approval works, and how to keep a studio's bill near zero.

A8gentAutomation practiceNovember 17, 202610 min read

Short answer: Mindbody's API is open to any developer account, and the studio does not need a special plan for it. Mindbody's developer portal lists $0.002 per call, free under 5,000 calls per billing cycle, billed monthly in arrears to the developer account. A well-built single-studio automation that uses webhooks often stays under the free threshold. Polling every few minutes is what runs up the bill.

Contents
  1. The Short Answer: What Mindbody Charges
  2. The Site ID Rule That Surprises Multi-Location Studios
  3. What the Mindbody API Can and Cannot Do
  4. How to Get Access: The Steps
  5. Three Automations Worth the API Fee
  6. If the API Is Not Worth It: Workarounds and Their Risks
  7. Time to Build and Running Cost
  8. What Breaks
  9. Want a Number Before You Build?
  10. Sources
  11. FAQ

The Short Answer: What Mindbody Charges

Mindbody's API pricing is not part of the studio's software plan. It is charged to whoever holds the developer account that makes the calls. If an agency or freelancer builds your integration on their own developer account, the invoice goes to them unless you agree otherwise. Settle that before the build.

Here is what Mindbody's developer portal showed on 17 November 2026, on its pricing card and its pricing FAQ:

ItemPublished priceNotes
Site access (the Public API)$0.002 per callListed as "Site Access" on the pricing card
Free tierFree under 5,000 calls per billing cycleThe card does not say whether calls above 5,000 or all calls are charged once you pass it. Ask API Support.
Consumer bookings$15.00 per location, per integration; $1.30 per class booking; $2.50 per appointment booking; virtual bookings freeListed under "Consumer Bookings", which applies to apps that take bookings from consumers
Public sandboxFreeFor testing
Custom sandbox$500 one-time without sample data, $1,000 with sample data, then $500 a yearOptional
Bulk discountNone"Not at this time"
ContractMonth to monthStop calling the API and the fees stop

The conflict you will find. Mindbody's older developer FAQ page still says there is "a 1,000 call limit per day" and that after it "you will be charged one third of a cent for every call". The pricing card and the newer pricing FAQ describe the 5,000-per-cycle model. The pricing FAQ also says "our billing system will automatically reflect the new rates", which suggests the card is current. Budget on the card, and ask API Support to confirm in writing.

The Site ID Rule That Surprises Multi-Location Studios

Mindbody's pricing FAQ is direct about this: "If you connect the integration to a Mindbody Site ID representing several locations, then you will incur API fees for all locations represented by that Site ID."

A Site ID is the studio account. A location is one physical site under it. One Site ID can cover many locations. So a chain that wants an automation for one new location, and connects it to the shared Site ID, pays location-based fees on all of them. The developer's invoice detail shows the call, location and booking counts per billing cycle.

To stop paying for a site you no longer need, the developer removes it in the developer portal under Account, Site Permissions, Remove Site.

What the Mindbody API Can and Cannot Do

Mindbody has two APIs that matter for a studio: the Public API, which you call, and the Webhooks API, which calls you. The table is drawn from Mindbody's Webhooks API documentation, checked 17 November 2026.

JobPossible?How
Know the moment an appointment is booked, changed or cancelledYesWebhook events appointmentBooking.created, .updated, .cancelled
Know when someone books or cancels a class, or joins a waitlistYesclassRosterBooking.created, .cancelled, classWaitlistRequest.created
Know when a new client signs up or a profile changesYesclient.created, client.updated
Know about sales, contracts and membershipsYesclientSale.created, clientContract.*, clientMembershipAssignment.*
Get full details after an eventYes, with a Public API callMindbody says the webhook only carries certain fields and you call the Public API for more
Book, cancel or add clients from outside MindbodyCheck before scopingThese are Public API write actions. We could not load the Public API v6 reference to confirm each one on 17 November 2026.
Rely on webhooks aloneNoMindbody recommends syncing cached data through the Public API every 24 hours

Rate limits. The Webhooks documentation says limits differ by endpoint, that your daily call limits are set when you receive your API key, and that you contact your account manager to raise them. Mindbody does not publish a per-second figure on the pages we read.

How to Get Access: The Steps

From the developer portal and the Webhooks documentation, checked 17 November 2026:

  1. Create a developer account at developers.mindbodyonline.com. Decide first whose account it is: the studio's or the builder's. That account gets the invoice.
  2. Build and test in the free sandbox.
  3. Request to go live. You fill in a short form about the integration. The portal says to "expect a response within 2 business days".
  4. Add a card. Mindbody requires one because fees are paid in arrears. Billing begins when you go live; fees start with your first live call.
  5. Get the studio to grant access. Mindbody's FAQ says the business gives the developer access "using an activation link or code". The studio owner completes this on their side.
  6. Create an API key on the API Credentials page, and for webhooks, create the subscription and set it to Active. New subscriptions start as PendingActivation.

Realistic time from start to live: a few days for access, if the approval comes back on time and the owner completes the activation promptly. Most of the calendar time is the build and testing, not Mindbody.

Three Automations Worth the API Fee

1. Late-cancel and no-show follow-up. An appointment or class cancellation event fires. The workflow checks the timing against your policy and sends a friendly rebook message, or flags a fee for staff to review. Never charge automatically without a human check.

2. Attendance drop-off alerts. A nightly job reads visit history and flags members whose visits have fallen off, so a coach can reach out personally. Our post on gym member attendance drop-off covers the logic.

3. Failed payment recovery. When a contract payment fails, the member gets a polite heads-up with a link to update their card, and the front desk sees a list. See gym failed payment recovery for the retry limits that matter.

Worked example: what one studio's API bill looks like

An illustrative single-location studio with about 40 bookings and cancellations a day. Two ways to build the same cancellation follow-up:

  • Polling: check three endpoints every 5 minutes. That is 3 x 288 x 30 = 25,920 calls a month. At $0.002 per call, about $52 a month, and more if the calls all count once past 5,000.
  • Webhooks: 40 events a day, each followed by about 2 Public API calls for details, is roughly 2,400 calls a month. Add a daily sync of about 50 calls, roughly 1,500 a month. Total about 3,900, under the 5,000 free threshold.

Same automation, same result, and one costs roughly nothing in Mindbody fees. These counts are assumptions for illustration; your real numbers show in the developer portal's billing reports.

If the API Is Not Worth It: Workarounds and Their Risks

For one studio with one simple job, a custom integration may not be worth it. Before building, check whether Mindbody's own messaging and marketing tools on your plan already cover the job.

Then check the apps in Mindbody's partner store. They already have API access, and if one does your job off the shelf, it is often cheaper than a custom build.

What we would not do: log into Mindbody with a bot and scrape the schedule, or export client lists by hand into an unsecured spreadsheet every week. Scraping sidesteps the access controls and the billing Mindbody has set up, so read Mindbody's terms first. A spreadsheet of names, phone numbers and membership status is personal data. If your studio also offers physiotherapy or other clinical services, health information may be involved, and you should ask any tool that touches it whether it signs a business associate agreement. We cannot give legal advice on that.

Time to Build and Running Cost

Market-typical ranges for small-business automation work in 2026, not a8gent prices:

  • Access: a few days, mostly waiting on go-live approval and the owner's activation.
  • One webhook-driven workflow: roughly $1,500 to $5,000 one-off, 1 to 3 weeks including testing in the sandbox.
  • Mindbody fees: $0 to a few dollars a month for a lean single-studio build; more with polling, multiple locations, or consumer bookings.
  • Hosting and messaging: roughly $0 to $50 a month for the workflow tool, plus texts or emails by usage.

See automation build cost for what moves a quote, and AI automation for gyms and fitness studios for the other jobs worth automating.

What Breaks

  • Webhook subscriptions switch themselves off. If your endpoint stops returning a success code, Mindbody deactivates the subscription and emails the developer account. If nobody reads that inbox, the automation dies quietly. Set the status back to Active after fixing it.
  • The bill lands on the wrong person. A freelancer's card expires or they move on, and the integration stops at the next billing failure. Hold the developer account in the business's name.
  • A shared Site ID multiplies fees. See the rule above.
  • Duplicate events. Log each event ID and skip ones you have processed, as Mindbody's docs suggest.
  • Drift. Without the daily sync, your copy of the data slowly falls out of step.

Want a Number Before You Build?

Tell us your locations, your Site ID setup and the one job you want automated. The free automation audit gives you an estimate of the call volume, the Mindbody fee, and whether an existing partner app already does it. If a build makes sense, our automation services team can build it on a developer account in your name and hand it over. Toast users can compare a very different model in our Toast API access guide.

Sources

All checked on Mindbody's developer portal on 17 November 2026.

  • Mindbody developer portal - pricing card ($0.002 per call, free under 5,000 calls per billing cycle, consumer booking prices), the pricing FAQ (Site ID rule, custom sandbox prices, billing in arrears, no bulk pricing) and the go-live step (response within 2 business days).
  • Mindbody developer FAQs - the older 1,000-calls-per-day wording and the activation link or code.
  • Mindbody Webhooks API documentation - event names, subscription activation, deactivation after failed deliveries, the 24-hour sync advice and rate limits.

FAQ

How much does the Mindbody API cost?
Mindbody's developer portal lists $0.002 per call for site access, with free API access for developers under 5,000 calls per billing cycle. Consumer bookings have separate prices. Fees are billed monthly in arrears to the developer account's card, in US dollars.
Who pays the Mindbody API fee, the studio or the developer?
The developer account that makes the calls. If your builder uses their own developer account, the invoice is theirs unless you agree otherwise. For a studio's own automation, hold the developer account in the business's name.
Do I need a particular Mindbody plan to use the API?
The developer pages we checked do not tie API access to a studio's subscription tier. The studio grants access with an activation link or code. If you are unsure your plan allows it, ask Mindbody support before paying for a build.
Why am I paying for locations that do not use the integration?
Mindbody bills by Site ID. If one Site ID covers several locations, Mindbody says you incur API fees for all of them. The developer can remove sites in the portal under Account, Site Permissions.
Does Mindbody have webhooks?
Yes. The Webhooks API pushes events such as appointment bookings and cancellations, class bookings, waitlist requests, new clients and sales. You create a subscription with an API key and set it to Active.
How long does Mindbody API approval take?
The developer portal says to expect a response to a go-live request within 2 business days. After that, the studio owner has to activate the connection on their side.
Is there a free way to test the Mindbody API?
Yes. The public sandbox is free. A custom sandbox costs $500 one-time without sample data or $1,000 with it, then $500 a year.

If this resonated

Module 02 is the long version of this post.

Eval set, refusal pattern, kill switch. Build it in a weekend.

All postsLast verified 2026-11-17

Done for you

Want this built for your business?

Tell us the workflow. We scope, build, and ship the agent with guardrails and the numbers to prove it worked. The scoping call is free.

Free scoping call. You own the code.

Request a scoping call