Momence API: Easier Than Mindbody, With Two Catches
A member who has not booked in three weeks is a retention opportunity, not just a row in Momence. Carly can notice the pattern and do the follow-through. It can reach out before a pack expires, respond to a new enquiry, handle cancellation or no-show communication from the inbox, and give the owner a concise daily or weekly picture of what needs attention.
Momence gives you API credentials in about a minute, with no approval step, no sandbox request, and no per-call fee. You create a public API client from the dashboard and start making calls.
For anyone who has been through Mindbody’s process — portal registration, a manual review, billing details, then a per-site activation the studio owner has to perform — that’s a genuinely different experience.
Then you look for webhooks and there aren’t any. The schedule is read-only too. So the studio that switched to Momence for the open API discovers its “when X happens, do Y” ambitions run through five thin triggers on an invite-only Zapier app.
What studios actually automate with it
With no webhooks and a read-only schedule, the honest split is between what can be checked and what has to come from elsewhere.
Works well by checking on a schedule:
- Members drifting away. Nobody has booked in three weeks — reaching them then is a very different conversation from reaching them at three months.
- Memberships and packs running out. A client is on their last credit, which is exactly the moment to renew them rather than after they’ve stopped coming.
- Daily and weekly summaries to the owner without anyone building a report.
Works better from your inbox and calendar:
- Cancellations and no-shows. Momence emails these; acting on the email gets you there faster than waiting for the next check.
- Class reminders and post-class follow-up, which are calendar-shaped anyway.
- New enquiries, which arrive as email long before they become a Momence record.
What you can’t do at all is create or move a class programmatically — the schedule is read-only, so anything that says “automatically add a class when X” isn’t possible here regardless of tooling.
Getting credentials
Dashboard → Apps & Integrations → Developer API → add a new public API client. Momence links straight to it at momence.com/dashboard/profile?host-redirect=public-api-clients.
No approval, no manual review, no partner application, no API agreement — none of it appears anywhere in the documentation. Create the client and go.
On plan gating: the word “API” does not appear on Momence’s pricing page at all, in any tier. Published tiers are Basic (free, with higher payment processing rates), Pro at $60/month, and Custom at $199/month. So no tier requirement is documented — though whether the Developer API section actually renders on a free Basic account isn’t something the docs confirm either way.
The mechanics:
- Base URL
https://api.momence.com, all routes under/api/v2/ - OAuth 2.0 with a token endpoint at
/api/v2/auth/tokenand three grant types:passwordfor staff automation,authorization_codefor customer-facing flows, andrefresh_token - The only scope is
public-api-v2 - Rate limits are barely documented — the entire spec defines just two, both on reports endpoints (100 per day for creating a report run, 1,000 per day for fetching one). There’s no global limit documented and no 429 response defined anywhere.
Access tokens expire in hours even while actively in use. Momence’s docs are explicit: “The access token you receive expires in a few hours after creation even when it’s being used, be sure to use refresh_token grant type.” A naive long-lived-token integration will break silently.
Permissions follow the human
There’s no scope system and no service account. Momence states it twice: “The API is always used by a specific user and all permissions are inferred from them,” and “All actions follow the same permission system as Host Dashboard.”
So a token minted from a limited front-desk login returns partial data — quietly, with no scope error explaining why. Mint keys from an account with the access the integration actually needs, and remember the key is tied to that person.
The schedule is read-only
This is the constraint most likely to break an assumption, because “Momence has a good API” and “I can manage classes programmatically” are not the same claim.
What you can write: create members; update name, phone, and email; assign and unassign tags; adjust membership credits; freeze and unfreeze memberships including scheduled freezes; run host checkout to sell memberships and packs; add a member to a session for free; add to a waitlist; check in and undo check-in; cancel session and recurring bookings. On the member side: checkout, addresses, saved payment methods, document signing, and self-cancellation.
What you can’t:
/host/sessionsis GET-only. You cannot create, edit, or cancel a class. The schedule is not writable./host/membershipsis GET-only. No creating membership or pricing products./host/appointments/reservationsis GET-only. No booking appointments through the host API.- No refunds endpoint, no staff management.
Also note GET /host/sales carries a warning in the spec: “This is an experimental feature, please contact support if you want to utilize this endpoint.”
One more shape to know: booking writes are free-only. POST /host/sessions/{id}/bookings/free adds someone at no charge. Taking payment means the multi-step checkout flow — prices, then compatible memberships, then checkout — and payment types can’t be mixed in one cart.
No webhooks. Five triggers, invite-only.
The spec contains zero occurrences of “webhook” — no top-level webhooks key, no callbacks, nothing. It’s a clean absence rather than an undocumented feature.
What exists instead is a Zapier app with five triggers:
- New Customer (first purchase)
- Membership Purchase
- Membership cancellation
- Event Booking
- Last Purchase with a Pack — a customer uses their final credit
Three constraints make this thinner than the list suggests:
- Triggers only, no actions. Momence’s own words: “While you can’t create actions in Momence via Zapier, you can create leads via the Momence API.” So Zapier can tell you something happened; it can’t do anything back.
- The app is unlisted. The public Zapier listing 404s while control listings resolve fine, and setup instructions say “accept the invite” — it’s a private app.
- Payloads are deliberately thin. Momence documents that the New Customer trigger “only provides a limited set of fields, such as First Name, Last Name, and Email… there is no way to access more granular data (such as phone numbers or purchase information). This limitation appears to be by design.”
So even the triggers you get hand you a name and an email, and anything more requires calling back into the API.
Momence versus Mindbody, honestly
| Momence | Mindbody | |
|---|---|---|
| Getting credentials | Self-serve, instant | Portal registration plus per-site activation |
| Approval step | None documented | Manual review |
| Per-call cost | None documented | Calls are metered |
| Webhooks | None | 31 event types |
| Schedule writes | Read-only | Writable |
The trade is real and it cuts both ways. Momence is far easier to get into and costs nothing per call. Mindbody makes you work for access and then meters you, but gives you a writable schedule and a proper event system.
If your integration is read-heavy — reporting, dashboards, syncing members outward — Momence is the easier platform by a wide margin. If it’s “react to things and change the schedule,” Momence will fight you.
Three credential systems, which is one too many
Momence has three unrelated credential paths, and mixing them up is the most common early confusion:
- The OAuth2 Developer API client — Apps & Integrations → Developer API
- A separate Zapier API key — Apps & Integrations → Integrations → Zapier
- A third Leads API token — Marketing → Leads → “Collect Leads using API”
Different keys, different locations, different docs.
Momence’s AI is real and walled off
Momence ships genuine AI: a Support Agent handling billing, freezes, refunds, bookings, waitlists, and check-ins; a Sales Agent requiring an active sales journey; and an AI Inbox. WhatsApp and voicemail channels are marked coming soon.
Two things worth knowing. The AI Agent add-on costs $399 a month — roughly twice the top published tier, and invisible on the pricing page. And there are no AI endpoints in the API at all. The agents live in Momence’s inbox UI and can’t be reached programmatically.
Getting the event to do something
With no webhooks and a read-only schedule, the automation story here has to be built out of polling plus the five Zapier triggers.
Handing that to an AI assistant doesn’t close the gap.
Scheduled work is available in ChatGPT and Claude Cowork, but their ordinary schedulers are clock-driven rather than generic listeners for changes in connected business apps. ChatGPT Workspace Agents add API-triggered runs, with another system responsible for detecting the event and making the call.
“Summarize which members are at risk of lapsing” is well within what ChatGPT or Claude will do with a Momence export. “Offer the waitlist spot the moment someone cancels” is not — and Momence won’t push you that event either, so something has to be checking.
Carly is built for the checking:
- Polls on a sensible interval and acts on what changed — the honest architecture when a platform ships no events, and precisely the bookkeeping worth handing off
- Fires on the Zapier triggers where they cover you — new customer, membership purchase or cancellation, event booking, last pack credit
- Fills in the thin payloads — a trigger that gives you a name and an email is only useful if something calls back for the rest, which is a step people skip
- Actually sends — Gmail and Outlook, with attachments
Because Momence exposes a public OAuth API, you can connect it natively to Carly from the Integrations tab. Carly can then use Momence in on-demand, recurring, and event-triggered workflows. AI agents start at $35/month, and workflow steps that don’t use AI run free.
Frequently Asked Questions
Does the Momence API cost anything?
No per-call fee is documented anywhere, and the word “API” doesn’t appear on Momence’s pricing page in any tier. Published tiers are Basic (free), Pro at $60/month, and Custom at $199/month. Whether the Developer API section renders on a free Basic account isn’t documented.
Does Momence have webhooks?
No. The OpenAPI spec contains no webhooks, callbacks, or subscriptions. The only outbound event triggers are five Zapier triggers — new customer, membership purchase, membership cancellation, event booking, and last pack credit — on an unlisted, invite-only Zapier app that supports triggers but no actions.
Can I create or edit classes through the Momence API?
No. The sessions endpoint is GET-only, so the schedule can’t be created, edited, or cancelled programmatically. You can book members into existing sessions, check them in, and cancel bookings, but not manage the schedule itself.
Is the Momence API easier to access than Mindbody’s?
Considerably. Momence credentials are self-serve and instant with no approval step and no per-call billing, where Mindbody requires portal registration, a manual review, and a per-site activation the studio owner performs. The trade-off is that Mindbody has webhooks and a writable schedule; Momence has neither.
Why does my Momence integration keep losing authentication?
Access tokens expire after a few hours even while in active use. Momence’s docs direct you to use the refresh_token grant rather than holding a long-lived token.
How much is Momence’s AI Agent?
$399 per month as an add-on, self-serve through Apps & Integrations. It isn’t listed on the pricing page, and its agents aren’t reachable through the API — they operate inside Momence’s inbox interface.
More: Mindbody API · Best AI workflow automation tools · Best AI agents for productivity
Ready to automate your busywork?
Carly schedules, researches, and briefs you—so you can focus on what matters.
See what people say
"Before Carly, I relied on a Calendly link, but the whole process felt impersonal and not very professional. Carly changed that by handling all the back-and-forth, so I'm no longer stuck in endless email threads trying to line up schedules.
Now Carly reaches out to candidates, shares my real-time availability, lets them pick a slot, then sends a Zoom link and drops it straight into my calendar. She sends reminders to both of us before each call, which has significantly reduced no-shows and last-minute confusion.
On top of scheduling, Carly acts like a full executive assistant, sending me my schedule the night before so I can prepare for each call. It reminds me of the old x.ai assistant, but Carly is noticeably smarter, faster, and better suited to my healthcare recruitment business."
