Gym and Studio Management Software APIs (2026)

If you are building a class booking app, a member portal, a payroll or marketing tool, or anything else that has to read and write a gym's members, classes and sales, the API you need is the one in the studio's management software. This page maps which of the platforms we checked on October 17, 2026 publish a developer API, how you get access, how requests authenticate, what the limits and prices are, and which push changes to you.

Everything below comes from each vendor's own pages, read on that date. Several vendors run their developer portals as JavaScript applications that returned no readable text to our fetch, and where that hid a fact we say so rather than fill the gap.

The short answer, platform by platform#

Our integration guides go deeper on the five with readable documentation: Mindbody, TeamUp, Mariana Tek, Wodify and ABC Glofox. Mindbody's per-call price has its own page: Mindbody API pricing.

Three ways studio platforms hand out API access#

The biggest difference between these APIs is not the endpoints. It is who decides that you may call them.

The business switches it on. TeamUp lets a staff member with the super admin permission create an API Application directly in the business dashboard, and its FAQ says free trial accounts can do it too. Wodify's documentation tells a gym where its API key lives in Wodify Core, and its API reference says to request one through the Web Integrations screen. For a developer working for one studio, this is the fastest route: the studio can grant access the same day.

The platform approves you, then each studio opts in. Mindbody's steps are a developer account, a request to go live, Mindbody's approval, and then an activation link or code from each business. Mariana Tek registers applications through its Integrations team, has you build against a sandbox tenant, and says a technical review before going live with a studio can take up to 1-3 weeks; production webhooks also need the studio owner's approval by email.

A partner program. ABC Fitness, whose site lists ABC Ignite, ABC Trainerize, ABC Glofox and ABC Evo, runs a partner program for app partners and solution providers. Its FAQ says you register at partners.abcfitness.com and ABC reviews the request, and that you qualify if you are an ABC customer with your own in-house developer, or a vendor supporting an integration for a mutual customer, able to meet ABC's infosec and data privacy policies. The program has several tiers, with terms discussed during evaluation and onboarding. ABC describes this as its "open API platform"; its developer portal returned only an error message to our fetch, so we could not read the API itself.

In our experience, the approval routes take weeks, not days, and they decide your launch date more than any endpoint does. If your product depends on Mindbody or Mariana Tek, start the approval while you build.

Authentication at a glance#

Every platform here expects its credentials to stay on your server:

• Header API keys. Mindbody uses an API-Key header plus a required User-Agent, and says all requests must come from your back-end servers because keys cannot be safely stored on mobile devices or websites. Wodify uses an x-api-key header. ABC Glofox sends three headers, x-glofox-branch-id, x-api-key and x-glofox-api-token, and says to always proxy them through a secure backend.
• OAuth. TeamUp recommends OAuth when your app acts for a customer or staff member, offers machine-to-machine tokens when it acts for the business, and says it does not support static API keys. Mariana Tek runs the OAuth 2.0 Authorization Code flow on each studio's own subdomain, with PKCE for single-page and mobile apps, and also issues API keys tied to a service account.
• Query-string keys. ClubReady's operation metadata lists an ApiKey parameter described as the key that "grants access to resources", alongside a StoreId.

If your users log in to book classes, OAuth is the route on TeamUp and Mariana Tek; on the API-key platforms, your server holds the key and enforces who may do what. The OAuth explainer covers the difference.

Limits, and what API access costs#

Mindbody is the only platform we checked that prints a per-call price, and the FAQ that prints it still describes the API as SOAP and XML web services, so confirm the current fee schedule before you budget. Its API Terms of Use add that fees are billed monthly, starting 30 days after you first receive access to a business's data. The details are on Mindbody API pricing.

None of these figures is the studio's own subscription to the platform. That is a separate bill the studio pays, which we have not reviewed.

Webhooks: which platforms push changes#

• Mindbody pushes events for bookings, clients, memberships, contracts, sales, staff and more, signed with an X-Mindbody-Signature header. It retries every 15 minutes for up to 3 hours, and recommends re-syncing cached data through the Public API every 24 hours.
• Mariana Tek posts events such as a new account, a reservation or a class check-in, after you request a subscription from its Integrations team.
• ABC Glofox lists webhook events for bookings, members, memberships, invoices and more in its API reference.
• TeamUp lists receiving event notifications with webhooks as a next step in its getting-started guide; we did not read its webhook pages.
• Wodify's documentation navigation does not mention webhooks, so plan to poll within its monthly quota.

Whichever you integrate, process events idempotently and keep a scheduled re-sync. Ingesting webhooks reliably covers the pattern.

The rest of the market#

• ABC Trainerize. Trainerize's own summary lists "API access for eligible Studio and Enterprise customers" and workflow automation through Zapier. Its help-center article on the API and webhooks refused our fetch, so we could not read the details.
• ClubReady. ClubReady serves a machine-generated list of operations, such as class bookings, check-ins and class schedules, with JSON, XML, JSV and CSV formats. Its class-schedule operation, for example, covers at most 7 days per request. How a developer obtains a key is not on any page we could read, and ClubReady's main site answered our fetch with an error.
• Zen Planner. Its integrations page says Zen Planner's "flexible API" lets businesses build custom integrations or connect proprietary tools, and lists Zapier among its integrations. We found no public API reference.
• PushPress. Its integrations page says integration partners are "curated by actual gym owners" rather than opened to thousands of integrations, and lists Zapier for syncing data with other systems. We found no public API reference.
• Exercise.com. Its custom development page offers custom integrations built by its team and Zapier consulting. We found no public API reference.
• Virtuagym and Sportivity. We found no current public API reference for either, and Sportivity's site returned no readable text to our fetch.

"No public reference found" means only that: some of these vendors may share documentation with customers or partners privately. Ask the vendor before you rule it out.

How to choose#

Our recommendation, in order:

1. Start from your customers' platforms. A studio rarely switches management software to suit an integration, so the platforms your customers already run decide which APIs you need.
2. Begin access work on day one. Self-serve platforms take a day; approval and review routes take weeks.
3. Check that the booking flow you need exists. Mindbody lists class registration and appointment booking, TeamUp's OAuth use cases include a customer website where users book spots, Mariana Tek's Customer API is built for custom booking and buying experiences, Glofox documents booking endpoints, and Wodify documents class reservations.
4. Design for push plus re-sync, within the terms. Mindbody's API Terms of Use, for example, prohibit caching its data for more than 48 hours, so a long-term copy of a studio's data may not be yours to keep.

For the general build-versus-buy question across fitness APIs, see fitness API vs building your own, and for every other category, the fitness API guide.