Mindbody API · unofficial, by Cotlet
Create your own Mindbody API
Mindbody: its API needs a developer account that Mindbody approves for live access (checked 20 Nov 2026). With Cotlet you can build your own. Do a job once with your AI agent in your Mindbody account, save it as an endpoint, and call it from n8n, Make, Zapier or your own code. Each endpoint runs in your own signed-in Mindbody session and returns only what your login can see.
Free 7-day trial, 2,000 credits, no card
Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by Mindbody. Mindbody is a trademark of its owner. If Mindbody's own integrations cover what you need, use them first.
curl -X POST "https://cotlet.dev/api/v1/custom/classes-for-day" \
-H "Authorization: Bearer $COTLET_API_KEY" \
-H "Content-Type: application/json" \
-d '{"date": "2026-11-21"}' const url = "https://cotlet.dev/api/v1/custom/classes-for-day";
const res = await fetch(url, {
method: "POST",
headers: {
Authorization: `Bearer ${process.env.COTLET_API_KEY}`,
"Content-Type": "application/json",
},
body: JSON.stringify({ date: "2026-11-21" }),
});
const { data } = await res.json(); import os
import requests
key = os.environ["COTLET_API_KEY"]
res = requests.post(
"https://cotlet.dev/api/v1/custom/classes-for-day",
headers={"Authorization": f"Bearer {key}"},
json={"date": "2026-11-21"},
)
data = res.json()["data"] {
"data": [
{
"time": "07:00",
"class": "Morning Vinyasa",
"teacher": "Dana R.",
"booked": 18,
"capacity": 20
},
{
"time": "12:00",
"class": "Lunch Pilates",
"teacher": "Sam K.",
"booked": 9,
"capacity": 14
}
]
} 01 Build
How do you build a Mindbody endpoint with Cotlet?
-
Sign in to Mindbody in your Cloud Browser.
You type your password yourself. Cotlet keeps the signed-in session, encrypted, never the password.
-
Do the job once with your agent.
For example: "List tomorrow's classes with the teacher, the bookings and the capacity."
-
Save it as an endpoint.
Give it a name, choose its inputs, such as a date or a teacher, and the fields it returns.
-
Call it with your Cotlet API key.
Each endpoint gets its own address,
POST https://. You send JSON in and get JSON back, from the same signed-in Mindbody session.cotlet.dev/ api/ v1/ custom/ <name>
02 Endpoints
Example endpoints you could build for Mindbody
Cotlet ships no fixed list of Mindbody endpoints. You decide which endpoints you build and what each one returns.
-
POST
/api/v1/custom/classes-for-day Classes for a day
Time, class, teacher, bookings and capacity for each class
-
POST
/api/v1/custom/members-due-back Members due back
Members with no visit in the days you name, with their last visit
-
POST
/api/v1/custom/ending-memberships Memberships ending soon
Client, membership and end date for each one
-
POST
/api/v1/custom/sales-summary Sales summary
Sales and refunds by product for a period
-
POST
/api/v1/custom/writesbook-client Book a client into a class
A booking for the client and class you name
A call to an endpoint you built could look like this:
curl -X POST "https://cotlet.dev/api/v1/custom/classes-for-day" \
-H "Authorization: Bearer $COTLET_API_KEY" \
-H "Content-Type: application/json" \
-d '{"date": "2026-11-21"}' The answer is JSON, with your fields under data:
{
"data": [
{
"time": "07:00",
"class": "Morning Vinyasa",
"teacher": "Dana R.",
"booked": 18,
"capacity": 20
},
{
"time": "12:00",
"class": "Lunch Pilates",
"teacher": "Sam K.",
"booked": 9,
"capacity": 14
}
]
} When you save an endpoint, Cotlet gives you its curl example and an OpenAPI description to paste into n8n, Make or your code.
03 Uses
What can you use your Mindbody endpoints for?
- Schedule Cotlet endpoint Slack or email
A morning report in n8n or Make.
Today's classes with bookings, and yesterday's sales, sent to Slack or email before the first class.
- Schedule endpoint Google Sheets
A member follow-up list.
Members due back and memberships ending, pulled into Google Sheets every Monday.
- Every 15 minutes endpoint front desk screen
A class board in your studio.
Today's classes and spots left, shown on a screen at the front desk.
- Voice or chat agent endpoint spots left
Your own AI receptionist.
A voice or chat agent that checks spots left in a class before it answers a client.
04 Access
What can an endpoint see and change?
An endpoint works in your own Mindbody session, so it can read and change only what your Mindbody login can. An owner login sees the whole business. A team login sees what its permissions allow. You choose what each endpoint does when you build it.
An endpoint that changes something, such as booking a client, first runs as a dry run: Cotlet shows you each request it would send, and nothing is sent. You allow the writes once in the Cotlet console and set a daily cap. A call over the cap fails whole, never half done.
05 Official API
Does Mindbody have an official API?
Mindbody has a public API for developers, but a developer account goes live only "Once Mindbody approves you for live access", and is then linked to each business (checked 20 Nov 2026). Mindbody's webhooks need the same live access. The full picture with sources: Does Mindbody have an API or MCP server?
Want ChatGPT or Claude to work in Mindbody instead of code? See the Mindbody MCP server.
06 Pricing
What does it cost?
- per successful call
- 10 credits
- when a call fails
- 0
- in the smallest pack
- ≈ 500 calls
- free trial, no card
- 7 days
A call to your endpoint costs 10 credits when it succeeds and nothing when it fails, with no browser minutes on top. Credits come in one-time packs from $29 for 5,000 credits, so a pack covers about 500 successful calls. The free trial gives you 2,000 credits for 7 days, no card.
Mindbody API with Cotlet: questions
Is this an official Mindbody API?
No. Cotlet is independent and not affiliated with Mindbody. The endpoints you build run in your own signed-in Mindbody account.
Do I need to code?
Not to build an endpoint: you do the job once with your agent and save it. To call it, you need a tool that sends HTTP requests, such as n8n, Make, Zapier or a script.
What happens when Mindbody changes its screens?
An endpoint works while Mindbody works the way it did when you built it. If Mindbody changes and a call fails, you get an email. After 3 failures in a row the endpoint turns off until you rebuild it with your agent or in the console. A failed call costs nothing.
How long can a call take?
Up to 90 seconds, and the answer can be up to 1 MB of JSON.
Build your first Mindbody endpoint
Sign in once, do the job with your agent and save it as an endpoint.
Try it free nowNo card. Takes about 5 minutes.