Cliniko · Rate Limits

Cliniko Rate Limits

Cliniko documents a fixed request rate limit of 200 requests per minute per user (per API key). Exceeding it returns HTTP 429 with an `X-RateLimit-Reset` response header carrying a UNIX timestamp for when the window resets. Cliniko also reserves the right to block requests that exceed fair-use allocation, and to block requests that omit a compliant `User-Agent` header (which must contain an app/vendor name and a valid contact email). List endpoints are paginated at 50 items per page by default and a maximum of 100 per page via the `per_page` parameter, which is the primary lever for reducing request volume.

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

It captures 3 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 Practice Management, Healthcare, SaaS, Rate Limiting, and Quotas.

3 Limits Throttle: 429
Practice ManagementHealthcareSaaSRate LimitingQuotas

Limits

Requests Per Minute user
requests
200 per minute per user
Documented published limit. 429 returned on exceed, with X-RateLimit-Reset.
Fair Use account
requests
not published (fair-use)
Requests beyond fair-use allocation may be blocked.
Pagination Page Size request
records
50 default, 100 max per page
Controlled by the per_page parameter on list endpoints.

Policies

Rate Limit Reset Header
429 responses include X-RateLimit-Reset, a UNIX timestamp for when the per-minute window resets.
User-Agent Enforcement
Requests without a User-Agent containing an app/vendor name and valid contact email may be automatically blocked.
Backoff Strategy
Clients should honor X-RateLimit-Reset, implement exponential backoff with jitter, and reduce request volume via larger per_page and q[] filtering.

Sources