Zus Health · Rate Limits

Zus Rate Limits

Zus documents a rate limit on the OAuth2 token endpoint of 200 token requests per hour per App Client for machine-to-machine flows; user authentication via username and password is not subject to this limit. FHIR search responses are paginated with a default page size of 10 resources, expandable up to 500. Bundle transactions accept up to 100 entries. Broader per-endpoint request rate limits for the FHIR API are not published and are not reconciled in this artifact.

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

It captures 4 rate-limit definitions, measuring requests, resources, and entries.

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

Tagged areas include Health, FHIR, Interoperability, Patient Data, and Healthcare.

4 Limits Throttle: 429
HealthFHIRInteroperabilityPatient DataHealthcareRate LimitingQuotasThrottling

Limits

Token Endpoint Requests app-client
requests
200 per hour
Machine-to-machine token requests per App Client; user/password auth is exempt.
FHIR Search Page Size request
resources
10 default, 500 maximum
Default page size 10, expandable up to 500 via _count.
Bundle Entries request
entries
100
Maximum entries per FHIR transaction or batch Bundle.
FHIR API Request Rate account
requests
see provider documentation
Per-endpoint FHIR request rate limits are not publicly documented.

Policies

Backoff Strategy
Clients should implement exponential backoff with jitter and honor Retry-After on 429 responses.
Token Reuse
Access tokens are valid for one hour (expires_in 3600); reuse tokens rather than re-minting to stay within the token endpoint limit.

Sources