Glofox has a partner API. Why would I use Integuru instead?

Glofox's partner API has no public application path and does not expose the full platform. Integuru's 16 verified Glofox actions come from the authenticated HTTP requests the Glofox web application already makes, so the timetable (list_classes, get_class, list_class_programs, list_courses), trainers, facilities and membership plans, and the signed-in member's bookings, credits, memberships and transactions are callable with your own studio login, with 24/7 on-call maintenance on the Production plan.

Can Integuru read more than one Glofox location?

Yes. Most catalogue actions accept branch_id, which overrides the studio on the session, so a franchise or multi-studio brand can query each location's classes, trainers, facilities and membership plans from one connected account and merge the results. The member-side actions (list_my_bookings, list_my_credits, list_my_memberships, list_my_transactions) read the signed-in member and are scoped to that account.

Does the Glofox integration support member check-in and access control?

For the signed-in member, yes. get_my_profile, list_my_memberships and list_my_credits return the membership state, remaining credits and profile a kiosk or door system needs to validate that member, and list_my_bookings confirms the class they are checking in to. A studio-wide roster or an attendance query across all members is not live; the Managed Service builds it on request.

Back to Integrations

Fitness & WellnessLive · 16 actions

Glofox API

Integuru provides a production-ready HTTP API for Glofox, covering 16 supported actions.

npm install -g integuru

Get started free

Backed by

100 API calls/month free

Verified actions live today

<3 sec

Response latency per call

99.9%+

Reliability rate on generated APIs

24/7

On-call maintenance on Production plans

Authenticates against: https://api.glofox.com/
Authentication: Login flows, including 2FA, handled by Integuru using your own Glofox credentials.
Approach: Direct HTTP requests, with no browser automation or RPA involved.

Endpoints

Available actions

Click an action to expand its parameters

Don't see the action you need?

The actions above cover the most common Glofox integration patterns, but they're not the full picture. Integuru can build additional workflows for any capability the platform exposes. Our Managed Service handles scoping, building, and maintaining custom actions on your behalf, so just let us know what you need.

Managed Service Get started free

Guide

Glofox integration guide

Last reviewed: September 2026

Overview

Integuru provides production-ready HTTP API access to Glofox. The actions listed on this page are currently supported by Integuru.

The 16 actions authenticate with your own Glofox login for one studio (branch_id) and cover two surfaces: the studio catalogue (classes, class programs, courses, facilities, trainers, membership plans and the studio record) and the signed-in account (profile, bookings, credits, memberships and transactions).

Does Glofox have a public API?

Glofox has a partner API, and it is not public. Access is granted case by case to partners, the documentation is not published, and the coverage stops short of the member records, attendance and class performance data that most integrations need. Integuru generates its Glofox actions from the authenticated requests the Glofox web app sends, using your own studio login.

Studio catalogue. get_studio returns the branch record. list_classes pages the timetable by start_date and end_date (default: today plus 14 days, up to 100 per page) and get_class returns one class. list_class_programs, list_courses, list_facilities with get_facility, list_trainers with get_trainer, and list_membership_plans with get_membership_plan cover the rest of what a studio publishes. Pass branch_id to read a different location than the one on the session.

Signed-in account. get_my_profile, list_my_bookings, list_my_credits, list_my_memberships and list_my_transactions read the authenticated member's own data, which is what a member app, a check-in kiosk or an access-control system needs to validate one member.

What is not live. A staff-side member roster, member creation and studio-wide attendance are not in the verified catalog. Glofox shows them to admin logins, so the Managed Service can build them for a studio account you control; they appear here once verified against live traffic.

Available Actions

The supported catalog currently includes list_my_bookings, list_classes, list_facilities, list_my_memberships, get_studio, list_my_credits, list_my_transactions, list_trainers, get_class, get_facility, get_trainer, get_membership_plan, get_my_profile, list_class_programs, list_membership_plans, list_courses.

Setup Notes

Configure Glofox credentials in Integuru once. Integuru manages authentication and session handling for subsequent API calls.

The session carries a default studio; pass branch_id on catalogue actions to read another location. Paged actions take page (1-based) and page_size (default 25, clamped to 100). list_classes defaults to a 14-day window from today in UTC.

Get started

Install the CLI and connect your Glofox login:

npm install -g integuru

Or sign in at app.integuru.com, add Glofox, and call the same 16 actions from the dashboard. For a staff-side roster, member creation or an attendance query this page does not list, the Managed Service scopes and builds it against your studio.

Good to know

Before you start

Can I use it today?: Yes. Every action listed above has been verified against live Glofox traffic. Install the CLI or sign in at app.integuru.com, connect your Glofox account, and start calling the endpoints.
What if Glofox changes or breaks?: On Production plans the Integuru team is on call around the clock, with auth auto-healing included, so target-platform changes get fixed by Integuru rather than by your engineers.
What does it cost?: Start on the Free plan at $0/month with 100 API calls/month. Production starts at $499/month with 24/7 on-call maintenance and auth auto-healing.

FAQ

Integration facts