The API Report CardAPI Index
GymMaster

GymMaster API

Gym & Health Club Management Software · gymmaster.com

GymMaster publishes REST/JSON APIs for members and bookings (Member Portal), door hardware (Gatekeeper), and reporting, plus webhooks and Zapier. Keys are self-issued per club from Settings, so multi-club integrations mean collecting a key from every site. Rate limits are unpublished.

Last verified: July 2026Fitness & Wellness
API GRADE
C
VERIFIED JUL 2026

SCORECARD

ExistenceGOODDocumented REST/JSON APIs: Member Portal, Gatekeeper for door hardware, and Reporting V2, plus a webhook manager.
AccessGOODKeys are self-issued per club from the Settings screen with no vendor approval step or extra fee.
CoverageGOODMembers, bookings, classes, payments, signup, door access, reports, KPIs, and dashboard widgets are all reachable.
AuthMIXEDThe portal API takes an api_key query parameter plus a login token; Gatekeeper uses HTTP Basic. No OAuth.
Docs & DXPOORNo published rate limits, and webhook retry policy is undocumented; delivery is push-only to a URL you host.
StabilityMIXEDv1 and v2 endpoints share one surface, and some responses are server-cached 2 to 10 minutes, hurting near-real-time reads.
Supergood: GymMaster has an API, with gaps. We cover what it's missing: stable endpoints, normalized JSON, managed auth.

Frequently asked questions

GymMaster scores C on the API Report Card. GymMaster publishes REST/JSON APIs for members and bookings (Member Portal), door hardware (Gatekeeper), and reporting, plus webhooks and Zapier. Keys are self-issued per club from Settings, so multi-club integrations mean collecting a key from every site. Rate limits are unpublished.

Tried to integrate with GymMaster?
SOURCES
API keys are issued per club through Settings → Integrations, which means each customer must turn on and share the key with the integrator, there is no aggregator/partner credential flow, making fan-out across many clubs operationally heavy gymmaster.com
Public documentation does not state rate limits or quota tiers, leaving integrators to discover them empirically gymmaster.com
Member Portal API mixes v1 and v2 endpoints in the same surface, with some operations cached server-side for 2–10 minutes, which complicates near-real-time use cases (e.g., reflecting a just-booked class) gymmaster.com
Webhook delivery is push-only to a customer-hosted URL, there is no managed event bus, retry policy is not publicly documented, and gym owners typically need a developer to stand up the receiver gymmaster.com
Reporting API V2 exposes 'available reports' by name/ID but report column selection and CURRENT/ALL/HIDDEN display modes are vendor-specific and undocumented outside of the on-platform Reports & Till UI, making programmatic parity with the in-app reports brittle gymmaster.com
Capterra reviewers report initial setup/configuration is time-consuming and the learning curve is steep, especially for staff onboarding capterra.com
Multiple reviewers flag that website-embedded signup and member-portal integration was difficult to get working, requiring back-and-forth with support capterra.com
Pricing is described as on the higher end for SMB gyms relative to lighter-weight alternatives, and member-count tier breakpoints (100 / 400 / 1,300) can force unexpected upgrades as a club grows g2.com
Some users report uncertainty about which release version they are on and slow visibility into the release-note stream g2.com
Implementation and data-migration fees from prior systems can be material ($300–$3,000 implementation, $500–$5,000 migration is commonly cited for gym software in this tier) gymdesk.com