Cal.com · Rate Limits

Cal Com Rate Limits

Cal.com API v2 returns 429 with a Retry-After header when rate-limit ceilings are exceeded. Limits are scoped per API key (or per OAuth client on Platform) and are not consistently published as exact per-second numbers. Self-hosted instances have no platform-imposed rate limit beyond the operator's infrastructure.

3 Limits Throttle: 429
ProductivitySchedulingCalendarOpen SourceBookingRate LimitingQuotasThrottling

Limits

Cloud API Key api_key
request · per-minute
published per-key
Per-key request rate; honor Retry-After on 429.
Platform OAuth Client oauth_client
request · per-minute
published per-client
Platform managed-user OAuth clients have their own ceilings; raised by contract.
Self-Hosted instance
none
-1
No platform-imposed limits when self-hosted; bounded by operator infrastructure.

Policies

Backoff Strategy
Exponential backoff with jitter on 429; honor Retry-After header.
Use Webhooks Not Polling
Subscribe to BOOKING_* events instead of polling the bookings endpoint.
Reserve Slots Before Confirmation
Use the Slots API to reserve a slot during the booking flow rather than re-querying availability multiple times.

Sources