Virtuagym · Rate Limits

Virtuagym Rate Limits

Virtuagym applies an account-level request cap on the Public API. Published guidance and integration references indicate requests are limited to roughly 500 per hour, and all Public API calls must be made over HTTPS (insecure connections are rejected). When a client exceeds the limit the API returns a custom throttling status (documented status code 421, "you tried to access the server too many times - wait a few minutes"), rather than the more common 429. Large data pulls are designed to be done incrementally: list endpoints accept a sync_from millisecond timestamp (return only records edited since a point) and a from_id cursor, plus max_results paging, which keeps sync workloads under the hourly cap.

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

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

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

Tagged areas include Fitness, Health Club Management, SaaS, Rate Limiting, and Quotas.

2 Limits Throttle: 421
FitnessHealth Club ManagementSaaSRate LimitingQuotas

Limits

Public API Requests account
requests
~500 per hour
Reported hourly request cap across the Public API for a club account.
Incremental Sync Window endpoint
records
paged
List endpoints use sync_from (ms timestamp), from_id cursor, and max_results to page large result sets within the hourly cap.

Policies

HTTPS Required
All Public API requests must use HTTPS; insecure HTTP connections are rejected.
Throttling
Exceeding the request cap returns status 421 (too many requests); back off and retry after a short wait.
Backoff Strategy
Clients should implement exponential backoff with jitter on throttling responses and prefer incremental sync (sync_from / from_id) over full re-pulls.

Sources