The Infrastructure for Unified Calendar Sync

The Nylas Calendar API lets you read, create, update, and manage calendar events across your users' existing calendars. Teams use it to build CRMs, scheduling workflows, internal tools, analytics dashboards, and AI-driven experiences — without managing provider-specific calendar integrations.

The Nylas Calendar API supports Google Calendar and Microsoft Outlook and Exchange, as well as other calendars available through compatible standard protocols.

Rather than building and maintaining two separate integrations — each with its own OAuth implementation, permission model, and API structure — you connect to Nylas once and access both providers through a unified API. Provider differences are abstracted at the Nylas layer.

Each provider has its own OAuth implementation, permission scope model, API structure, and deprecation cycle. Building directly means your team owns all of that complexity for every provider you support. The Nylas Calendar API handles provider differences through one integration, reducing the engineering surface area significantly.

Yes. You can create, update, cancel, and delete calendar events — including titles, descriptions, attendees, times, locations, and reminders. Changes sync directly to the user's connected calendar.

Yes. The Nylas Calendar API allows you to read past and upcoming events, subject to permissions granted by the user. This supports use cases like activity timelines, reporting, automation, and AI context building.

You can query availability and free/busy data to understand when users are available without exposing full event details. This is commonly used for scheduling logic, capacity planning, and workflow automation.

Yes. Changes made in your application or in the user's calendar provider are reflected in both directions, keeping your product and the user's calendar aligned in real time.

The API supports event creation, updates, and cancellations; recurring event structures; free/busy queries; multiple calendars per user account; conferencing link generation for Google Meet, Zoom, and Microsoft Teams; and two-way sync with supported providers.

The API supports event updates and cancellations, and provides webhook events to notify your application when calendar data changes — making it straightforward to keep systems in sync and respond to real-time updates.

The Calendar API is the data layer — it reads events, syncs calendars, and checks availability. The Scheduler is the booking layer — it surfaces availability to external users, handles booking logic, and creates confirmed meetings. Most scheduling products use both together.

Access is controlled through provider-specific permissions granted during user authentication. The Nylas Calendar API abstracts these differences while ensuring your application only accesses the calendar data users explicitly authorize.