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, in the API Commons Rate Limits shape.

It captures 3 rate-limit definitions, measuring requests and domains.

An exhausted limit returns HTTP 429.

This profile was written by API Evangelist and has not been verified against a page the provider published; treat every limit as unconfirmed until a dated transcription replaces it.

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 Exhausted: HTTP 429
Method: generated, dated 2026-07-03.
Written by API Evangelist on 2026-07-03 and not verified against a page the provider published. Treat every limit as unconfirmed until a dated transcription replaces it.
View Source
FitnessGym ManagementRate LimitingQuotas

Limits

Live Account Requests account
requests
10 requests/second, burst allowance of 1000 requests
Applies to production (live) API credentials.
Sandbox Account Requests account
requests
3 requests/second, burst allowance of 300 requests
Applies to sandbox/development API credentials.
Payment Collector Domain Authorization integration
domains
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.

Sources

Work with this as data

Every rate limit here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for rate limits

4 MCP tools reach this
  • find_rate_limitsBrowse and filter every rate limit in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This rate limit 
curl "https://apis.io/api/v1/rate-limits/glofox-rate-limits"
All rate limits 
curl "https://apis.io/api/v1/rate-limits?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.