- A per-minute limit, enforced on every call, that refuses a call outright once it’s spent.
- For an organization’s workspace plan, a per-month request allowance — see Usage and billing for how that one behaves (Essential is billed for going over, never blocked; only a contracted Enterprise hard cap can refuse a call for this reason).
Per-minute limits today
A clinic-owned key on the Team tier has no monthly request cap — only the 60-per-minute limit above. If you’ve seen a “100,000 requests a month” figure mentioned anywhere for a clinic’s own key, that was never enforced and doesn’t reflect a real limit; ask us if you’re unsure which limit actually applies to your integration.
How the limit works
The per-minute limit is a bucket that holds a minute’s worth of requests and refills continuously. A key limited to 60 per minute can send 60 requests at once. After that it gets one more request back every second (the limit divided by 60), so a steady 60 a minute never meets the limit, and a burst is refused only for as long as the bucket takes to refill. Some routes that do heavy work, such as starting an import, also have a tighter limit of their own. A clinic connected to several organizations has a limit per connection. A refusal from one of those names it withlimit_kind (for example
"route").
Reading the headers
Every response, including a refusal, carries headers telling you where you stand:
Watch
RateLimit-Remaining and slow down before it reaches zero, rather than waiting to be told.
When you go over the per-minute limit
You get a429 with code: "rate_limited". Retry-After gives the seconds until your next request will be accepted,
and RateLimit-Remaining is 0:
Retry-After and retries a 429 on any method.
Respect Retry-After exactly rather than retrying on a fixed interval — retrying too eagerly against a 429 just extends the wait for everyone using that key.
A
429 with code: "quota_exceeded" is a different limit — a contracted Enterprise workspace’s monthly allowance, not this per-minute bucket. See Errors and Usage and billing.Designing around the limit
- Cache what you can. Availability and catalogue data don’t need to be fetched on every page view of your own site — cache it and refresh on an interval, or in response to your own traffic patterns.
- Use
updated_sinceon list endpoints (see Pagination) so a periodic sync only pulls what changed, instead of the whole catalogue every time. - One key per integration, not one key shared across unrelated systems — each gets its own bucket, and a runaway process in one doesn’t starve another.