Calendly · Rate Limits

Calendly Rate Limits

Calendly applies request rate limits to the v2 Scheduling API and the Webhook API. The developer portal references rate limiting in its docs but the per-second / per-minute thresholds are served from a JavaScript-rendered Stoplight viewer that is not directly extractable; consumers should consult the live documentation for current numbers. Rate limits are scoped to the access token / OAuth application and apply across the production API. The Free plan does not include API access, so rate limits practically only affect Standard, Teams and Enterprise customers.

Calendly Rate Limits is the machine-readable rate-limit profile for Calendly on the APIs.io network, in the API Commons Rate Limits shape.

It captures 2 rate-limit definitions, measuring requests_per_minute and retries_per_failed_event.

An exhausted limit returns HTTP 429.

This profile was written by API Evangelist and has not been verified against a page the provider published; treat every limit as unconfirmed until a dated transcription replaces it.

The profile also includes 4 backoff/retry policies defined and response codes documented for throttled, quotaExceeded, and serviceUnavailable.

Tagged areas include Scheduling, SaaS, and Rate Limiting.

2 Limits Exhausted: HTTP 429 Quota: 429
Method: generated, dated 2026-05-05.
Written by API Evangelist on 2026-05-05 and not verified against a page the provider published. Treat every limit as unconfirmed until a dated transcription replaces it.
View Source
SchedulingSaaSRate Limiting

Limits

Scheduling API requests access-token
requests_per_minute
see developer.calendly.com Stoplight docs
Rate is bound to the OAuth access token / personal access token. Exceeding it returns HTTP 429.
Webhook delivery retries subscription
retries_per_failed_event
see developer.calendly.com webhook docs
Calendly retries failed webhook deliveries with exponential backoff before disabling the subscription.

Policies

Token-Scoped Limits
Rate limits are enforced per access token. OAuth applications should distribute calls across user tokens rather than concentrating them on a single service token.
Backoff on 429
When HTTP 429 is observed, retry with exponential backoff and jitter. Do not loop tightly.
Webhook Retries
Calendly retries failed webhook POSTs on a backoff schedule and eventually disables the subscription if the endpoint stays unreachable. Endpoints should respond 2xx promptly and process asynchronously.
Pagination Discipline
Use cursor pagination on list endpoints rather than aggressive polling to stay well under the published ceiling.

Sources

Work with this as data

Every rate limit here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for rate limits

4 MCP tools reach this
  • find_rate_limitsBrowse and filter every rate limit in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This rate limit 
curl "https://apis.io/api/v1/rate-limits/calendly-rate-limits"
All rate limits 
curl "https://apis.io/api/v1/rate-limits?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.