Yes, Calendly has an API. Its REST API v2 covers scheduling, contacts and Notetaker data, alongside webhooks and embeds. You sign in with OAuth 2.1 for public apps or a personal access token for a single account. Limits are 50 requests a minute for each user on the Free plan and 500 on higher plans, as of Nov 2026.
Three building blocks for developers
Calendly's developer portal offers APIs to connect Scheduling, Contacts and Notetaker data, which is its meeting recaps, with your own product. There are three building blocks, and which one you'll need depends on the job you've got in mind.
| Tool | What it does | Good for |
|---|---|---|
| REST API (v2) | Book meetings and read and write Scheduling, Contacts and Notetaker data | Syncing bookings into your systems |
| Webhooks | Real-time notifications for Scheduling, Contacts and Notetaker events | Reacting the moment someone books |
| Embeds | A scheduling page on your site via a snippet of HTML: inline, popup or button | Booking without leaving your site |
If all you want is a booking page on your website, an embed may be all you need, with no code beyond the snippet. If you want your CRM to update when someone books, webhooks are the efficient route, because Calendly tells you instead of you asking every few minutes.
Personal access token or OAuth?
Calendly has two authentication types, and the choice comes down to how many accounts your tool will touch. Personal access tokens suit a single account. Calendly's examples are internal tools like a reporting dashboard, or pushing event and invitee data into your own CRM. OAuth 2.1 is for public applications where Calendly members share their account data, and it's required whenever you need multiple accounts.
So a script for your own business uses a personal access token, and that's the quickest way to get started. A product you sell to other Calendly users needs OAuth. There's no way to stretch one personal token across a team of separate accounts.
The rate limits
- Free plan: 50 requests a minute for each user, as of Nov 2026.
- Higher plans: 500 requests a minute for each user.
- OAuth tokens: each user can request only 8 within 1 minute.
- Going over returns HTTP 429, with X-RateLimit headers.
Two details matter. The limits are enforced per user, not per app. And they apply to direct API calls and to calls made through third-party integrations alike. If you've connected several tools to the same Calendly user, they're all drawing from that one allowance, so a busy CRM sync can slow down a reporting tool you'd forgotten about.
The limit that catches booking tools
Calendly Developer Docs single out the Create Event Invitee endpoint, the one that creates bookings. It has its own, much tighter limits: 5 requests a day for each user on Free and Trial, and 500 a minute for each user on Enterprise, with the plans in between capped per minute, hour and day. If you're planning to book meetings programmatically on a Free account, five a day is the real ceiling, so test against it before you promise anything to a client.
Building something reliable
Use webhooks for anything that needs to happen when a booking changes, and keep API polling for occasional reads such as a nightly report. Read the X-RateLimit headers on each response so you can slow down before you hit a 429. And if your tool books on behalf of users, check which plan each user is on, since the invitee limit varies so much. My explainer on APIs versus webhooks covers the polling question in more depth.
How Cal.com compares
Cal.com's API v2 documents its rate limits by authentication method, with API keys at 120 requests per minute. If you're weighing up booking tools more widely, my list of Acuity Scheduling alternatives covers more of the field.
Want AI doing the heavy lifting in your marketing?
I build the systems that handle the boring 80 percent, so you get your week back. Done properly, with the human kept in.
My verdict for small businesses
Calendly's API is a good fit for syncing bookings into a CRM, building reports and reacting to new meetings with webhooks. Start with a personal access token for your own account, lean on webhooks rather than polling, and read the Create Event Invitee limits before you build anything that books for people. For ideas on using Calendly in your wider marketing, see my Calendly marketing strategy guide.
Want your tool on this list? Featured spots and reviews here are paid partnerships. Here's how to partner with me.
Frequently asked questions
Does Calendly have a public API?
Yes, a REST API v2 with webhooks and embeds.
How do I authenticate?
Personal access tokens for one account, OAuth 2.1 for apps used by many accounts.
What are the rate limits?
50 requests a minute for each user on Free and 500 on higher plans, as of Nov 2026.
Can I create bookings through the API?
Yes, via the Create Event Invitee endpoint, which has tighter limits.
Is there real-time notification support?
Yes, through webhooks.
