Calendly APIConnect Calendly without building on its API
Calendly has a REST API. Self-serve on any Calendly plan including Free, except a few Enterprise-only endpoints, while webhooks need a paid Standard, Teams, or Enterprise plan. If you're reading the docs because you need Calendly to talk to the rest of your stack, Caddi does that without you writing or maintaining integration code: you show it the job once, and it runs it across Calendly and your other tools.
- APIREST (JSON)
- AuthOAuth 2.0
- AccessSelf-serve
What the Calendly API gives you
- Type
- REST (JSON)
- Authentication
- OAuth 2.0 (public apps) or personal access token (internal use)
- Who can get access
- Self-serve on any Calendly plan including Free, except a few Enterprise-only endpoints, while webhooks need a paid Standard, Teams, or Enterprise plan.
- What it covers
- Users, organizations, event types, availability, scheduled events and invitees (including booking through the Scheduling API), webhooks, contacts, and Notetaker data.
- Limits
- 500 requests per user per minute on paid plans and 50 on Free, with tighter limits on Create Event Invitee (e.g., 10/min, 50/hour, 100/day per user on paid non-Enterprise plans).
- Worth knowing
- No endpoint reschedules an event or invitee, and cancelling works on a whole event but not on one invitee in a Group event.
Official docs: developer.calendly.com. Checked September 2026. Vendors change access terms, so confirm with Calendly before you build.
Building on the Calendly API vs. having Caddi run it
| The job | Build it on the API | With Caddi |
|---|---|---|
| Getting access | Register an app, get Calendly credentials, and manage tokens and refreshes. | Connect your Calendly account once. Caddi holds the connection. |
| Writing the integration | A developer maps fields, handles pagination, retries and rate limits, and writes the sync. | You show Caddi the Calendly task the way you'd train a new hire. It writes verified code for it. |
| Steps the API doesn't cover | Screens with no endpoint stay manual, or need a separate RPA tool. | Caddi uses a secure, audited browser session where there's no API, in the same automation. |
| The other systems in the loop | Each extra tool is another API, another set of credentials, another integration to own. | One automation runs across all the tools the job touches. |
| Keeping it running | Someone owns the code when the API version, fields or your process change. | Every automation is reviewed before it runs in production, and every run is logged. |
Building on the API is the right call when you have engineers and the integration is your product. When the goal is getting Calendly work off someone's desk, the build is the slow part.
What teams usually want the Calendly API for
Booked-meeting CRM logging
When a Calendly meeting is booked, Caddi creates the right CRM event, links it to the contact, and posts the agenda to the owner.
Meeting prep packet
An hour before each meeting, Caddi assembles the prep packet from the CRM, the planning tool, and recent email — and sends it to the host.
Follow-up flow
After the meeting, Caddi writes a structured note to the CRM, opens any committed follow-up tasks, and confirms next steps with the attendee.
Calendly API questions
Does Calendly have an API?
Yes. Calendly has a REST API, authenticated with OAuth 2.0 (public apps) or personal access token (internal use). The official documentation is at https://developer.calendly.com/.
How do I get access to the Calendly API?
Self-serve on any Calendly plan including Free, except a few Enterprise-only endpoints, while webhooks need a paid Standard, Teams, or Enterprise plan.
Does the Calendly API have rate limits?
500 requests per user per minute on paid plans and 50 on Free, with tighter limits on Create Event Invitee (e.g., 10/min, 50/hour, 100/day per user on paid non-Enterprise plans).
Can I connect Calendly to my other tools without writing code against its API?
Yes. With Caddi you show the Calendly task once, the way you'd train a new hire, and Caddi builds it as verified code that runs across Calendly and the other tools the job touches. Where a step has no API, Caddi uses a secure, audited browser session in the same automation.
Do I need a developer to automate Calendly with Caddi?
No. There is no integration code for you to write or maintain. Every automation Caddi builds for Calendly is reviewed before it runs in production, and every run is logged.
Connect Calendly without the build.
Drop your work email and pick a time. We'll show you Caddi running your Calendly workflow end to end.