Momence · Rate Limits

Momence Rate Limits

Momence does not publish fixed numeric rate limits for its Public API in the developer documentation as of the review date. Access is gated by OAuth2 with per-host public API clients (client_id / client_secret), and tokens are short-lived (access tokens expire within hours and must be refreshed via the refresh-token grant), which bounds long-running automation. Clients should assume standard throttling protections may apply and handle 429 responses with backoff. Numeric per-client or per-endpoint request ceilings are not documented.

Momence Rate Limits is the machine-readable rate-limit profile for Momence on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 2 rate-limit definitions, measuring requests and duration.

The profile also includes 2 backoff/retry policies defined and response codes documented for throttled.

Tagged areas include Fitness, Wellness, Studio Management, Rate Limiting, and Quotas.

2 Limits Throttle: 429
FitnessWellnessStudio ManagementRate LimitingQuotas

Limits

Public API Requests client
requests
not published
No fixed numeric request-rate limit is documented for the Public API.
Access Token Lifetime token
duration
short-lived (hours)
Access tokens expire within hours and must be refreshed with the refresh-token grant.

Policies

OAuth2 Client Gating
Every call is authenticated with an OAuth2 token issued to a dashboard-created public API client; unauthenticated or expired-token calls are rejected.
Backoff Strategy
Clients should implement exponential backoff with jitter and honor Retry-After on any 429 responses.

Sources