ezyVet · Rate Limits

Ezyvet Rate Limits

ezyVet enforces request-rate limits on its API at two levels. Individual endpoints are typically throttled at around 60 requests per minute, and a global ceiling of roughly 180 calls per minute applies per database per partner. Requests over the limit return HTTP 429. Every response carries the x-ratelimit-remaining and x-ratelimit-reset headers so clients can track their remaining quota and back off before being throttled. OAuth bearer tokens have a 12-hour TTL and must be refreshed before expiry.

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

It captures 3 rate-limit definitions, measuring requests and seconds.

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

Tagged areas include Veterinary, Practice Management, PIMS, Rate Limiting, and Quotas.

3 Limits Throttle: 429
VeterinaryPractice ManagementPIMSRate LimitingQuotas

Limits

Per-Endpoint Request Rate endpoint
requests
~60 per minute
Endpoint-specific throttle; exact value can vary by endpoint.
Global Request Rate database-partner
requests
~180 per minute
Applies per practice database per partner across all endpoints.
Access Token Lifetime token
seconds
43200 (12 hours)
OAuth 2.0 Client Credentials bearer token TTL; refresh before expiry.

Policies

Backoff Strategy
On HTTP 429, honor x-ratelimit-reset and retry with exponential backoff plus jitter.
Token Refresh
Cache the 12-hour bearer token and refresh it before expiry rather than requesting a new token per call.
Header Awareness
Read x-ratelimit-remaining on every response and throttle client-side before hitting the limit.

Sources