Wellnessliving Rate Limits
WellnessLiving's official OpenAPI specification (github.com/wellnessliving/openapi) embeds a machine-readable `x-rate-limit` extension directly on most operations, so - unusually for a partner-gated API - numeric limits are confirmed straight from the published spec rather than inferred. Of 324 documented paths in the production build, 458 operation-level rate-limit entries were found (some operations expose both GET and POST): the overwhelming majority (454) are capped at 200,000 requests per hour, with a small number of high-load schedule/class-listing operations further restricted to 3,000 requests per 5 minutes. The API additionally supports an opt-in `X-Error-Rules` request header that converts internal error statuses into real 4xx HTTP codes (by default every response is HTTP 200 with the error encoded in the JSON body), which matters for building correct retry/backoff logic against throttling responses.
Wellnessliving Rate Limits is the machine-readable rate-limit profile for WellnessLiving on the APIs.io network, in the API Commons Rate Limits shape.
It captures 4 rate-limit definitions, measuring requests and n/a.
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 2 backoff/retry policies defined and response codes documented for throttled.
Tagged areas include Fitness, Wellness, Rate Limiting, and Quotas.
generated, dated 2026-07-03.
Limits
Policies
Sources
- https://github.com/wellnessliving/openapi
- https://www.wellnessliving.com/developer-portal/getting-started/introduction/
- https://www.wellnessliving.com/developer-portal/getting-started/api-usage/
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.