Glofox · Rate Limits
Glofox Rate Limits
Glofox publishes fixed numeric rate limits for its partner/developer API in the Authentication section of its developer portal. Limits differ between live (production) and sandbox accounts and are enforced with a token-bucket style burst allowance on top of a sustained requests-per-second cap.
Glofox Rate Limits is the machine-readable rate-limit profile for Glofox on the APIs.io network, conforming to the API Commons Rate Limits specification.
It captures 3 rate-limit definitions, measuring requests and domains.
The profile also includes 3 backoff/retry policies defined and response codes documented for throttled.
Tagged areas include Fitness, Gym Management, Rate Limiting, and Quotas.
3 Limits
Throttle: 429
FitnessGym ManagementRate LimitingQuotas
Limits
Live Account Requests account
10 requests/second, burst allowance of 1000 requests
Applies to production (live) API credentials.
Sandbox Account Requests account
3 requests/second, burst allowance of 300 requests
Applies to sandbox/development API credentials.
Payment Collector Domain Authorization integration
pre-approved only
The hosted Payment Collector iframe must have its origin domain authorized by Glofox before it will load.
Policies
Throttle Response
Requests exceeding the sustained or burst limit receive an HTTP 429 response, documented in the portal's error-handling reference as "Throttle Down."
Legacy Success-False Responses
Some older endpoints return HTTP 200 with a success:false body field instead of a 4xx/5xx status; the portal recommends normalizing these to 400 in client middleware.
Backend-Only Credentials
x-api-key and x-glofox-api-token must be used only in backend integrations and proxied through a secure server - never called directly from a browser or shipped in client-side code.