There are three kinds of calendar API and the price gap between them is three orders of magnitude. Provider-native APIs (Google, Microsoft, CalDAV) cost nothing and reach one calendar system each. Unified APIs (Nylas from $15 a month, Cronofy from $819) normalize several behind one contract. Booking platform APIs (Cal.com, Calendly, meetergo) hand you an availability engine and a booking flow you don't maintain.
Which you need turns on a question the category pages skip: how much of the work between calendar access and a finished booking is yours. Below are the eight you'll shortlist with current prices, then that work item by item.
Key Takeaways
- Provider-native is free, and that's the smallest line in the budget. Google's Calendar API carries no charge for standard use (checked 2026-11-16). The cost is the sync, token and availability code you own afterwards.
- Unified pricing scales per connected calendar, not per API call. Cronofy's entry plan is $819 a month billed annually and API calls are unlimited, so the per-account ceiling is what you model.
- Ask who owns double-booking. If the answer is "we do", you need a calendar API. If you'd rather it were somebody else's on-call rotation, you need a booking API.
- Authorization is the integration, not a step in it. Google and Microsoft each want their own consent screen, scopes, refresh handling and app review.
What a calendar API gives you, and what it leaves on your desk
A calendar API is read and write access to a calendar system: list calendars, create and update events, invite attendees, query free/busy. Google, Microsoft and the CalDAV standard all expose roughly that shape, and the unified vendors expose it once across several providers.
What none includes is the decision layer. Free/busy tells you a block is occupied. It doesn't tell you that the booker's 14:00 is the host's 15:00 in a week when only one country has changed its clocks, that a 30 minute slot needs a 15 minute buffer after it, or that two people clicking the same slot must not both get it.
Calendar API comparison at a glance
| API | Category | Providers covered | Entry price (checked 2026-11-16) |
|---|---|---|---|
| Google Calendar API | Provider-native | No charge for standard use | |
| Microsoft Graph | Provider-native | Outlook, Exchange Online, Microsoft 365 | Included with a licensed mailbox |
| CalDAV | Open standard | iCloud, Fastmail, Nextcloud, any CalDAV server | No charge, self-implemented |
| Nylas | Unified | Google, Microsoft, Exchange, iCloud | $0 free tier, $15 a month paid |
| Cronofy | Unified | Google, Microsoft, Exchange, Apple | $819 a month billed annually |
| Cal.com API | Booking platform | Via the platform's own connections | $0 for one user, $12 per user a month |
| Calendly API | Booking platform | Via the platform's own connections | No scheduling API on Free |
| meetergo | Booking platform | Google, Outlook, Apple, Proton | REST API and MCP on every plan, Free included |
Google Calendar API
Google Calendar is the best documented calendar API in the category and where most teams start. What you won't get is anything outside Google: an Outlook user is a second integration project, not a configuration change.
Read the quota numbers before you design your sync. Standard use is 10,000 requests a minute per project and 600 a minute per user per project, on a sliding window, so a burst in one minute throttles you in the next, and the daily billing threshold of 1,000,000 requests per project cannot be raised on request. Charging above the request limits is planned for later in 2026 with at least 90 days' notice, and quotas now differ by project age: projects created on or after 1 May 2026 get the newer numbers (all checked 2026-11-16).
| Plan | Price |
|---|---|
| Standard use | No charge (checked 2026-11-16) |
| Above the request limits | Charges planned for later in 2026, 90 days' notice promised |
Customer Reviews
No review platform rates the Calendar API itself, only Google Workspace, so there is no rating with a sample size to cite here (checked 2026-11-16).
Best for: products whose users are overwhelmingly on Google Workspace, and teams who want the sync logic in their own repository.
Microsoft Graph calendar API
Microsoft Outlook calendars are reached through Microsoft Graph, which adds two things Google handles differently: a findMeetingTimes call that proposes slots, and a getSchedule call that returns free/busy for users, rooms and distribution lists in one request. If your product books meeting rooms, that last one is the reason to be here.
The cost is the enterprise shape of it. In a tenant with admin consent policies your app waits on an administrator before any user can connect, and throttling is layered: 130,000 requests per 10 seconds per app across all tenants is the global ceiling, the Outlook service applies its own per-app-per-mailbox limits on top, and the first limit reached triggers the throttle (checked 2026-11-16).
| Plan | Price |
|---|---|
| Graph calendar endpoints | No separate charge, requires a licensed Microsoft 365 mailbox (checked 2026-11-16) |
Customer Reviews
As with Google, no review platform rates the Graph calendar endpoints as a product (checked 2026-11-16). Evaluate the throttling documentation instead.
Best for: products selling into Microsoft 365 tenants, especially where rooms and resources are part of the booking.
CalDAV and Apple iCloud
CalDAV is the open standard behind the calendars that aren't Google or Microsoft: iCloud, Fastmail, Nextcloud and most self-hosted servers. Specified in RFC 4791, it's the only route to Apple calendars, because Apple publishes no documented public REST API for iCloud Calendar. Expect XML over HTTP with WebDAV verbs, behaviour that varies between server implementations, and no vendor to escalate to.
| Plan | Price |
|---|---|
| CalDAV against any compliant server | No charge, implementation is yours (checked 2026-11-16) |
Customer Reviews
A protocol has no review page, and that's the signal: support quality depends on the server, not a vendor. meetergo's own CalDAV integration covers the calendars the two big providers don't.
Best for: supporting Apple and self-hosted calendar users once the Google and Microsoft paths already work.
Nylas
Nylas puts one REST contract in front of Google, Microsoft, Exchange and iCloud, with free/busy, availability, webhooks, virtual calendars and a notetaker API on top. The part that catches teams out is the shared Google OAuth app: using Nylas's instead of registering and verifying your own is a paid add-on, and only on the annual Pro plan.
| Plan | Price |
|---|---|
| Free | $0 a month, 5 connected accounts |
| Essentials | $15 a month, 10 email and calendar plus 10 calendar-only accounts |
| Pro (monthly / annual) | $49 a month / $43 a month, 25 email and calendar plus 35 calendar-only accounts |
| Enterprise | Volume band pricing, on request |
| Accelerator Package add-on | $2,400 a year, annual Pro plans only |
Prices checked 2026-11-16. A HIPAA and HITECH BAA and an uptime SLA sit on the Enterprise tier.
Customer Reviews
Nylas holds 4.0 out of 5 from 59 reviews on its G2 review page, small-business accounts about two thirds of the sample (checked 2026-11-16). G2's side-by-side with Cronofy has reviewers rating Cronofy higher on ease of setup, administration and support.
Best for: products that need email and calendar from the same integration, and teams who want a free tier to prototype against.
Cronofy
Cronofy sells calendar connectivity as infrastructure and prices like it: availability across many participants, two-way sync, meeting rooms, Enterprise Connect for Exchange estates, a choice of six data centres, a 99.99% uptime guarantee and an MCP server so agents can book through the same engine. The caveat is the floor. There's no cheap tier to experiment on, and what you model is the per-synced-account overage, because API calls are unlimited on every plan.
| Plan | Price |
|---|---|
| Emerging | $819 a month billed annually, up to 500 synced accounts |
| Growth | $2,399 a month billed annually, up to 3,000 synced accounts |
| Strategic | On request |
| Extra synced accounts | $1.39 each a month (Emerging) or $0.69 each (Growth) |
Prices checked 2026-11-16.
Customer Reviews
Cronofy rates 4.7 out of 5 from 52 reviews on G2, 82% five stars and 17% four (checked 2026-11-16). The recurring praise is implementation support rather than the API surface, which fits a product bought by integration teams on a deadline.
Best for: SaaS platforms embedding scheduling for enterprise clients, where data residency choice and an SLA have to be in the contract.
Cal.com API
Cal.com comes at this from the other direction: an open-source scheduling platform whose API drives bookings, event types and availability, with OAuth and API key authorization and embeddable React components for the front end. Because the platform owns the calendar connections, you inherit its availability engine instead of writing one. Check the gating: custom API access arrives on the Teams tier, so the free plan is for evaluating the product rather than building on it. We cover how the Cal.com API behaves in practice separately.
| Plan | Price |
|---|---|
| Free | $0, one user |
| Teams (yearly) | $12 per user a month, includes custom APIs |
| Organizations (yearly) | $28 per user a month, adds further API access |
| Enterprise | On request |
Prices checked 2026-11-16.
Customer Reviews
Review platforms cover the Cal.com scheduling product, not its API, and no rating with a verifiable count for the API turned up on 2026-11-16. Self-hosting is the substitute: read the code before committing.
Best for: teams who want a booking engine they can host and modify, on a per-seat subscription.
Calendly API
Calendly has a v2 API covering event types, scheduled events, invitees and organization membership, useful when the booking pages live in Calendly and your product needs to read what happened. It's a reporting surface more than a booking engine, and the scheduling API and custom webhooks are not in the free plan, so an integration starts at a paid seat.
| Plan | Price |
|---|---|
| Free | $0, one event type, one calendar connection, no scheduling API |
| Standard (yearly) | $10 per seat a month |
| Teams (yearly) | $16 per seat a month |
| Enterprise | From $15,000 a year, 50 seats minimum, USD only |
Prices read from the pricing page with yearly billing selected, checked 2026-11-16.
Customer Reviews
Calendly's thousands of reviews are reviews of the scheduling product; no separate rating and count for the developer API turned up on 2026-11-16, so its score is evidence about the booking pages, not the integration.
Best for: organizations already standardized on Calendly that need booking data in a warehouse or CRM.
meetergo
meetergo exposes the booking engine rather than a raw calendar. Its REST API covers over 100 endpoints across bookings, availability and calendar connections, plus CRM, documents and client portals (checked 2026-11-16), and the calendars connect on the platform side for Google, Outlook, Apple and Proton, feeding the unified calendar view that availability queries read from. Tokens are scoped per area, so a key issued for scheduling gets a 403 on a CRM call.
In practice the integration is three calls: issue a scoped key, GET availability for a meeting type, POST the booking with the invitee's details. The confirmation, the calendar write and the reminder workflow then happen without you, with webhooks for event-driven work and round robin and routing forms assigning hosts platform-side. The MCP server (@meetergo/mcp-server, MIT licensed) ships over 60 tools including get_availability, book_appointment, reschedule_appointment and cancel_appointment (checked 2026-11-16), the shortest route to an assistant booking against real availability instead of guessing. The company is German, hosts in Nuremberg, is GDPR compliant and includes a DPA, which answers the first question a European legal team asks about holding other people's calendar data.
Where it isn't the answer: meetergo is not a unified calendar API. If your product needs to read arbitrary events out of a customer's Google calendar for your own features, that's Nylas or Cronofy territory. The public feature page also publishes no base URL, auth scheme, webhook catalogue or rate limits, so budget a session with the developer documentation before you estimate.
| Plan | Price |
|---|---|
| Free | €0 a month, up to 3 people, REST API and MCP server included |
| Light | €12.90 per person a month |
| Suite | €99 a month, 3 people included |
| Premium | €179 a month, 3 people included |
| Enterprise | From 30 seats, price on request |
Regular list prices with yearly billing, excluding VAT, checked 2026-11-16. The paid plans have a 7 day trial with no card and the Free plan has no time limit, so you can issue a key and call the booking endpoint from your own code before deciding anything.
Customer Reviews
meetergo publishes a 4.8 rating from OMR Reviews and G2 without a review count alongside it, and neither platform reviews the API separately (checked 2026-11-16). A rating without its sample size isn't evidence, so test the endpoints on the free plan instead.
Best for: European teams who need a finished booking workflow, data processing in the EU, and an API and MCP server to drive it from their own product.
What sits between calendar access and a working booking flow
Here is the work you take on when you choose a calendar API over a booking API. Each item is somebody's sprint:
- Availability intersection. Free/busy for one person is a query. Free/busy for a round-robin pool, with per-host working hours, per-event-type durations and a buffer either side, is a solver you write and then debug for a year.
- Time zones and DST. Store the zone, not the offset, and expand recurrence in the host's zone. The bug reports arrive in the weeks when one continent has changed its clocks and the other hasn't.
- Recurring events. RRULE expansion, exceptions, cancelled instances in a series. Every provider models this differently.
- Double booking. Two people click the same slot in the same second. You need a lock or an idempotency key at the write, because the calendar provider will accept both. Our write-up on how double bookings happen covers the failure modes.
- Token lifecycle. Refresh, revocation, password changes, withdrawn admin consent, re-consent when scopes change. Every failure is a user whose bookings quietly stop arriving.
- Sync freshness. Push subscriptions have to be created, renewed and recovered after a gap. Polling instead makes the staleness window and the rate limit the same problem, which is where one backend thread on building a calendar app against the Google API ends up.
- The booking experience. Slot picker, confirmation and cancellation pages, reschedule links, reminders, payment at booking, the ICS file. None of it is in any calendar API.
- Data protection duties. Store other people's calendar events and you're a processor for them. That's a DPA, a retention policy and a deletion path, not a library.
The same requirement, three ways
Take a brief: one booking link, three possible hosts, a deposit at booking, reminders, and reschedule without emailing anyone.
On a provider-native API you own all eight items above and support one calendar vendor at launch. On a unified API items one to six get easier, seven and eight stay yours, for a floor of $819 a month at Cronofy or $15 at Nylas depending on scale; you still build the booking pages and take the payment. On a booking platform API all eight are the vendor's problem and your work is calling an endpoint and styling an embed, at the price of the booking UI and your place on their roadmap.
The demand side says it in plainer words. In a 40-comment thread in r/smallbusiness someone rebuilding a trades website asks what to use rather than what to build, and in a 90-comment thread in r/ShortTermRentals, the advice that lands is to price the do-it-yourself route against the hosted one first.
How to choose
Four questions, in this order.
- Read calendars, or create bookings? Reading someone's week to show it inside your app is a calendar API requirement and nothing else will do. Putting a meeting on the books is a scheduling requirement, and the booking platforms have already written it.
- How many providers at launch? One, and provider-native is cheaper with more control. Two or more, and the unified vendors have absorbed the differences in event models, recurrence and free/busy that would otherwise be your next two quarters.
- Who carries the on-call? Sync breaks at 3am in somebody's time zone. Decide whether that page goes to your team or to a vendor with an SLA.
- Whose jurisdiction holds the data? If your buyers are European, residency and a DPA belong in the shortlist criteria, not in a security review three weeks before launch. Cronofy sells a choice of data centre, and meetergo processes in the EU by default.
If those four land you on "we needed a booking page, not an integration", start from the hosted free tiers: our guide to what the free scheduling plans include compares them, and embedding a booking calendar on a website is a shorter path than any of the eight APIs here. If it lands the other way and you want the engine without the pages, meetergo's scheduling app is callable from day one of a free account.
Call a booking engine instead of building one
Call a booking engine instead of building one
Frequently asked questions
What's the difference between a calendar API and a scheduling API?
A calendar API reads and writes calendar data: events, calendars, free/busy. A scheduling API owns which slots are offerable and what happens when one is taken, so it carries the availability rules, buffers and host assignment. Most teams searching for the first are describing the second.
What's the best free calendar API?
Google's, if your users are on Workspace: standard use carries no charge today (checked 2026-11-16). For multi-provider work, Nylas's free tier at 5 connected accounts is the usual prototyping route, and meetergo's REST API and MCP server are on its Free plan.
Are free calendar APIs secure and reliable enough for production?
The authorization model is identical on the free and paid tiers, so security comes down to your own token storage. Reliability is where they differ: Google publishes quotas but no SLA for standard use, and the uptime guarantees and BAAs sit on the enterprise tiers at Nylas and Cronofy.
Which calendar APIs support both Google and Outlook in one integration?
The unified vendors, Nylas and Cronofy, plus the booking platforms that handle connections on their own side. With provider-native APIs you build and maintain each separately, including two sets of OAuth scopes and two app reviews. What varies between unified vendors is how they normalize recurrence exceptions, all-day events and attendee responses, which don't map cleanly between Google and Microsoft.
How much does a calendar API cost?
Provider-native access is free today, with Google planning charges above its request limits later in 2026. Unified APIs price per connected account, from $15 a month at Nylas to $819 a month billed annually at Cronofy. Booking platform APIs price per seat, $0 to $28 per user a month across the options here (all checked 2026-11-16).
Is there an official Apple iCloud calendar API?
No documented public REST API. iCloud calendars are reached over CalDAV as specified in RFC 4791, one of the clearer reasons to pay a unified vendor rather than build it.
Can an AI agent book meetings through a calendar API?
It can create an event, but it can't tell whether the slot was offerable. That's why the booking-side vendors shipped MCP servers: Cronofy, Google's Calendar MCP server and meetergo's @meetergo/mcp-server put availability and booking behind tools an agent calls, keeping the rules on the server instead of in a prompt.








