Skip to content
MyGymDesk logoMyGymDesk
Menu

MyGymDesk Website API (API access)

MyGymDesk’s Website API has twelve REST endpoints behind one per-gym key. It covers lead capture into the CRM, live pricing, class/service catalogs and timetables, bookings, shop checkout and membership purchase with server-verified payment. Docs at mygymdesk.in/developers.

What you can do with it

Put a working enquiry form on your own website

POST a visitor’s name and phone from your site’s contact or ‘book a trial’ form to the lead-capture endpoint, and the enquiry appears instantly in Leads → Enquiries, de-duplicated by phone number.

Show always-current membership prices and a class timetable

Fetch live pricing and the weekly class schedule from the read endpoints so your marketing site reflects what’s configured in MyGymDesk instead of hand-maintained HTML. Cache server-side to stay within the rate limit.

Take a paid class booking from your site, end-to-end

Create a Razorpay order via the booking endpoint, run Checkout in the browser, then record the booking only after MyGymDesk verifies the capture on the gym’s own gateway — the amount is resolved server-side, so a leaked key can’t mint free bookings.

Sell bookable services online

List active, published services with member and non-member pricing, and take payment for physio, massage or court-hire bookings with the same server-side verification as classes.

Route multi-branch leads and schedules

Filter the display endpoints by location to render one branch’s timetable, and let captured leads file against the branch configured on the key.

How to set it up

  1. 1As the owner (or a staff member with the ‘Manage Integrations’ permission), open Settings → Growth & Apps → Integrations.
  2. 2Select the ‘Website Integration’ sub-tab. A key is auto-created the first time you open it — it starts inactive.
  3. 3Flip the toggle in the tab header to ON. Until it’s on, every API request returns a 403 and the configuration fields stay hidden.
  4. 4Copy the revealed key immediately from the ‘Your New API Key’ panel — it’s shown exactly once (stored only as a hash). If lost, use ‘Regenerate Key’, which invalidates the old key instantly.
  5. 5Set ‘Assign Leads to Location’, the hourly rate limit (default 30 requests/hour, shared across all endpoints), and ‘Allowed Origins’ (full origins with scheme, e.g. https://www.yourgym.com), then save.
  6. 6Use the in-tab code snippets or open the full endpoint reference at mygymdesk.in/developers, and send the key from your server in the x-mgd-api-key header.

Frequently asked questions

What can the MyGymDesk API actually do?

It’s a Website API with twelve REST endpoints: capture leads into the CRM, read membership and package pricing, read class and service catalogs plus a weekly timetable, check authoritative session prices, and take class or service bookings with server-verified Razorpay/PayPal payment. It is not a general read/write API over all your gym data — there’s no members, attendance or billing CRUD. The Leads endpoint is included on the Pro plan; the rest need the Enterprise plan or the Full Website API add-on.

How does authentication work and where do I get a key?

Each gym has one key (format mgd_live_ plus 32 characters). Generate it in Settings → Integrations → Website Integration, toggle it on, and copy it once — it’s stored only as a hash. Send it from your server in the x-mgd-api-key header (or a ?key= query param).

What limits should I plan around?

The default rate limit is 30 requests/hour shared across all endpoints per key, so cache the pricing and timetable endpoints and raise the limit before a public launch. There’s one key per gym, one payment gateway per gym, and the timetable is a weekly template whose session IDs change over time.

Ready to use API Access with MyGymDesk?

Free 7-day trial. No credit card required.