Cronofy · Rate Limits

Cronofy Rate Limits

Cronofy advertises unlimited API calls on its paid API tiers and does not publish fixed numeric per-second or per-minute request quotas in its public developer documentation. To protect the platform, Cronofy applies abuse protection and may throttle abnormal traffic, returning HTTP 429 when a client is temporarily rate limited. The batch endpoint caps a single request at 50 sub-requests. Specific numeric limits are not reconciled in this artifact.

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

It captures 2 rate-limit definitions, measuring requests.

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

Tagged areas include Scheduling, Calendar, Availability, Booking, and Productivity.

2 Limits Throttle: 429
SchedulingCalendarAvailabilityBookingProductivityRate LimitingQuotasThrottling

Limits

Request Throttling account
requests
not publicly published (unlimited API calls advertised; protective throttling applies)
Cronofy may return 429 when abnormal or abusive traffic is detected.
Batch Sub-Requests request
requests
50
The batch endpoint allows up to 50 requests to be submitted in a single call.

Policies

Abuse Protection
Cronofy throttles abnormal traffic to protect platform stability even though paid tiers advertise unlimited API calls.
Backoff Strategy
Clients should implement exponential backoff with jitter and honor Retry-After on 429 responses.

Sources