Back to Home
Developer Portal
Ship partner apps, signed webhooks, and branded mobile releases from one tenant-routed platform.
HexaFit keeps members, operations, and integration traffic on the tenant host. That means fewer routing edge cases, cleaner auth boundaries, and a smb gym experience that matches the same operational source of truth as the admin surfaces.
FITNESS GYMMEMBERSHIPSINGLE LOCATION
A partner stack with real launch lanes
Tenant-routed APIs, sandbox guides, signed webhooks, branded mobile lanes, and webhook replay controls give partners a real platform surface instead of a PDF integration kit.
Tenant HostSigned WebhooksSandboxMobile APIsSMB Gym routing
All API requests resolve tenant scope from hostname. SMB Gym traffic, members, and mobile APIs stay on the tenant host directly.
Integration contracts
Connector health, tests, replay controls, signed webhooks, and partner event redrive are productized capabilities for members and operator workflows.
Mobile API
Native members flows run through `/api/mobile/*` for login, dashboard, QR access, preferences, wallet passes, and pay-now.
Self-serve apps
Tenant admins can register developer apps, issue app keys, rotate webhook secrets, and pull sandbox onboarding guides from the integration console.
Partner Tracks
Build on the same control plane HexaFit uses internally
Embedded operator apps
Build internal tools for staff, franchise operators, finance teams, and support desks using the same tenant-routed data plane as HexaFit itself.
Signed webhook automation
Subscribe to lifecycle events for revenue, retention, check-ins, and device activity with signature-safe delivery and replay controls built in.
Branded mobile releases
Launch tenant-specific member apps with preview, QA, and store lanes tied to the same branding and environment model as the product UI.
Hardware + edge extensions
Attach bridges, scanners, access systems, kiosks, and point-of-sale surfaces without breaking tenant routing or introducing side-channel hosts.
Routing Model
Environment -> Gateway -> Tenant -> Route
Tenant host
https://{tenant}.app.{env}.gohexafit.comUse this for members, signup, tenant UI, and `/api/*` calls.
HQ host
https://hq.app.{env}.gohexafit.comUse this only for HexaFit platform control-plane and HQ-only workflows.
Door and device route
https://{tenant}.app.{env}.gohexafit.com/api/door/*Door devices never send `tenantId` in the request body. Scope comes from hostname.
API Contracts
Current members and developer endpoints
MethodRoutePurpose
POST/api/mobile/loginMember mobile login
GET/api/mobile/dashboardMember dashboard summary
GET/api/mobile/qrShort-lived access QR token
POST/api/mobile/pay-nowIdempotent open-balance payment
PUT/api/mobile/preferencesPush and messaging preferences
POST/api/mobile/wallet/issueApple or Google wallet pass issuance
GET/api/developer/apps/meVerify a developer app key against the tenant host
GET/api/enterprise/integrations/developer-eventsDiscover subscribable partner-event contracts
PUT/api/enterprise/integrations/developer-appsRegister or update a developer app
POST/api/enterprise/integrations/developer-apps/{appId}/rotate-credentialsRotate API key and webhook signing secret
GET/api/enterprise/integrations/developer-apps/{appId}/sandboxGenerate tenant-specific sandbox onboarding instructions
Self-Serve Flow
What the partner platform now productizes
Register a developer app from the integrations console with webhook URL, scopes, and subscribed event types for your smb gym rollout.
Store the issued API key and webhook signing secret in the partner secret manager immediately.
Verify the key on the tenant host with `/api/developer/apps/me` before moving into deeper contracts.
Use `/api/public/schedule`, `/api/public/discovery`, and `/api/mobile/*` to connect public discovery, members experiences, and sandbox automation before enabling webhook delivery.
Launch Rail
From first sandbox call to live tenant rollout
StageWhat happens
Register appCreate the app, choose scopes, issue credentials, and point HexaFit at the partner webhook URL.
Verify tenant hostUse `/api/developer/apps/me` on the tenant hostname to prove routing, auth, and environment selection are correct.
Load sandbox guidePull a tenant-specific sandbox pack with sample headers, payloads, checklist steps, and public probe examples.
Promote to productionTurn the same app into a live tenant integration with rotated credentials, signed webhooks, and release-lane signoff.
Webhook Packs
Signed event families that map to real operator workflows
Billing + revenue events
Subscriptions, invoices, payment attempts, recurring collections, and payout-facing lifecycle changes for revenue automation.
Member + lifecycle events
Signup, profile, agreement, and engagement changes for CRM, loyalty, and retention workflows.
Access + device events
Door, QR, check-in, and hardware activity for real-time facility operations and audit trails.
Branded Mobile
One member app shell from sandbox to store release
LaneWhat happens
Preview buildUse Expo/EAS preview lanes to validate branding, navigation, and tenant-routed mobile APIs before rollout.
Internal QALock dark/light modes, push preferences, wallet passes, and member billing flows against the tenant host.
Store releasePromote the same branded member shell into App Store and Play Store submission once design and operations are approved.
Platform Guarantees
Operational rules already baked into the product
Tenant host first
Partner traffic stays on the tenant host so embedded apps, public discovery, member flows, and device APIs all share the same routing truth.
Replay-safe delivery
Event delivery is built for retries, redrive, idempotency, and signature validation instead of assuming best-case network conditions.
Sandbox without fake topology
Partners test against the real environment and hostname model instead of learning one routing shape in dev and another in production.
Migration adapters
The migration layer already includes source adapters for Mindbody, Glofox, TeamUp, Zen Planner, PushPress, WellnessLiving, and Wodify.