Calendly API
A well-documented v2 REST API at api.calendly.com covers events, invitees, routing forms, and webhooks, with OAuth 2.1 for apps and personal access tokens on paid plans. Limits are 60 requests per minute on most tiers, and webhooks skip a first-class rescheduled event.
Frequently asked questions
Calendly scores C on the API Report Card. A well-documented v2 REST API at api.calendly.com covers events, invitees, routing forms, and webhooks, with OAuth 2.1 for apps and personal access tokens on paid plans. Limits are 60 requests per minute on most tiers, and webhooks skip a first-class rescheduled event.
Calendly has an official API, but teams routinely hit its limits: gated access, partial coverage, or paid tiers. Most end up supplementing it with exports or an unofficial API layer like Supergood.
Calendly is a SaaS meeting-scheduling platform that lets individuals and teams publish bookable availability links, coordinate one-on-one / group / round-robin / collective meetings, and automate the entire pre-meeting workflow (intake questions, routing forms, reminder emails/SMS, video conference link generation, calendar invites, post-meeting workflows).
Horizontal scheduling automation, with disproportionate adoption inside three functional verticals: (1) outbound sales / SDR / AE workflows (where Calendly links sit in every email signature and sequence, and round-robin routing distributes inbound demo requests across reps); (2) recruiting and talent (where coordinators use Calendly to schedule phone screens, panels, and onsites across multiple interviewers and candidate timezones, often integrated with Greenhouse/Lever ATSes); (3) customer success / professional services / onboarding (kickoff calls, QBRs, support escalations). A team admin sets up Calendly users, connects each user's Google/Outlook/Exchange calendar (up to six per user), and configures event types (15-min intro, 30-min demo, 60-min onsite panel, etc.) with custom availability rules, buffers, daily limits, and intake questions.
Extreme. Calendly is effectively the genericized verb for meeting scheduling in B2B SaaS, 'send me a Calendly' is now a noun-verb shorthand the way 'Zoom me' became one.
Calendly holds the meeting source-of-truth for the teams that run on it: every booked meeting's invitee details (name, email, phone, custom intake answers, UTM parameters, IP geolocation), full meeting history with timestamps and outcomes (booked, canceled, rescheduled, no-show), event-type configuration (durations, prices for paid events, intake forms, routing logic), routing-form submissions with lead scoring and rep assignment, team availability windows and round-robin weights, calendar-conflict checks across connected Google/Outlook/Exchange calendars, video-conference URLs and recordings metadata, reminder and follow-up workflow logs, and the connective tissue feeding Salesforce/HubSpot CRM records with meeting-booked timestamps.
Mature and actively modernized. Calendly was founded in 2013 by Tope Awotona and reached unicorn status in 2021 with a $3B valuation on a $350M OpenView-led round.
Rate limits are tight, 60 req/min on Standard/Teams forces backoff for any meaningful bulk sync; the 2x bump on Enterprise (120/min) is still modest for large org backfills. Webhooks fire for invitee.created and invitee.canceled but there is no first-class 'rescheduled' webhook event; integrators must reconcile cancel+create pairs themselves. Full sourced list under Sources below.
Common alternatives include Cal.com, Acuity Scheduling, SavvyCal, Chili Piper, HubSpot Meetings, Microsoft Bookings. Graded alternatives appear under "More from the report card" below.
Grades measure one thing: can a customer's engineering team get their own data out programmatically? We check six things (whether a real API exists, how access is gated, data coverage, auth quality, docs and developer experience, and stability) and roll them into a letter grade. Grades get re-verified, and they only move on evidence.