Google Calendar API
Browse all Google APIs✓ Official Vendor SpecProductivityCalendar Schedulingoauth237 EndpointsREST
For Agents
Create and manage calendar events, check attendee availability, and set up recurring schedules across Google Calendar accounts. Supports 37 operations covering events, ACLs, and real-time change watches.
Use for: I need to create a calendar event with multiple attendees, Check availability for a meeting time across several people, I want to set up a recurring weekly event, List all events for today on a specific calendar
Not supported: Does not handle email delivery, file storage, or video call infrastructure — use for calendar event scheduling and availability queries only.
Create, modify, and query calendar events with attendee management, recurring event rules, and free/busy availability lookups across Google Calendar accounts. Access 37 endpoints covering event creation, calendar sharing, access control lists, real-time change notifications, and cross-calendar availability checks. Supports recurring events with RRULE syntax, timezone-aware scheduling, and video conferencing link generation.
Install Jentic One Beta
Connect the Calendar API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Calendar API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Calendar API.
Create calendar events with attendees, locations, video conferencing links, and reminders
Query free/busy availability across multiple calendars for meeting scheduling
Set up recurring events using RRULE syntax with exceptions and modifications
Watch for calendar changes in real time via push notifications to webhook endpoints
Share calendars with configurable access levels from free/busy-only to full owner control
Import and export events in iCalendar format for cross-platform synchronization
Retrieve event lists with time range, search query, and single-event expansion filters
Use Cases
Patterns agents use Calendar API for, with concrete tasks.
★ AI Agent Meeting Scheduling
AI agents use the Calendar API through Jentic to find available time slots, create meetings with attendees, and handle rescheduling requests. An agent searches Jentic for 'check calendar availability,' receives the freebusy.query schema, and executes the lookup across multiple calendars — no OAuth configuration needed. Handles timezone conversions, attendee conflict detection, and Google Meet link generation automatically.
Query free/busy availability for three attendees over next week using POST /freeBusy, find the first shared 1-hour slot, then create an event at that time with a Google Meet link
Event Management and Recurring Schedules
Create and manage complex recurring event schedules using RRULE syntax with support for exceptions, modifications to individual instances, and timezone-aware start/end times. The events.insert endpoint accepts full RFC 5545 recurrence rules and generates individual event instances that can be independently modified or cancelled. Supports all-day events, multi-day spans, and events with attachments.
Create a recurring weekly team standup event every Monday at 9:00 AM for 30 minutes with 5 attendees using POST /calendars/{calendarId}/events with recurrence rule RRULE:FREQ=WEEKLY;BYDAY=MO
Calendar Sharing and Access Control
Manage calendar visibility and access permissions programmatically through the ACL endpoints. Grant users specific access levels from freebusy-only to full owner control, share calendars with groups or domains, and audit current permissions. Supports delegation scenarios where assistants manage executive calendars with appropriate access boundaries.
Grant writer access to a secondary calendar for user assistant@company.com using POST /calendars/{calendarId}/acl with role='writer' and scope type='user'
Real-Time Calendar Sync
Subscribe to push notifications for calendar changes using the events.watch endpoint, enabling real-time synchronization between Google Calendar and external systems. Receive notifications when events are created, modified, or deleted without polling. Combined with incremental sync tokens, this enables efficient one-way or bidirectional calendar synchronization with external scheduling tools.
Set up a watch on a calendar's events using POST /calendars/{calendarId}/events/watch with a webhook URL, then poll for changes since the last sync token using GET /calendars/{calendarId}/events with syncToken
Key Endpoints
37 endpoints — create, modify, and query calendar events with attendee management, recurring event rules, and free/busy availability lookups across google calendar accounts.
METHOD
PATH
DESCRIPTION
POST
/calendars/{calendarId}/events
Create a new calendar event
GET
/calendars/{calendarId}/events
List events with time range and query filters
GET
/calendars/{calendarId}/events/{eventId}
Get a specific event by ID
PATCH
/calendars/{calendarId}/events/{eventId}
Update event details
DELETE
/calendars/{calendarId}/events/{eventId}
Delete an event
POST
/freeBusy
Query free/busy availability for calendars
POST
/calendars/{calendarId}/events/watch
Subscribe to event change notifications
POST
/calendars/{calendarId}/acl
Create an access control rule
POST
/calendars/{calendarId}/events
Create a new calendar event
GET
/calendars/{calendarId}/events
List events with time range and query filters
GET
/calendars/{calendarId}/events/{eventId}
Get a specific event by ID
PATCH
/calendars/{calendarId}/events/{eventId}
Update event details
DELETE
/calendars/{calendarId}/events/{eventId}
Delete an event
POST
/freeBusy
Query free/busy availability for calendars
POST
/calendars/{calendarId}/events/watch
Subscribe to event change notifications
POST
/calendars/{calendarId}/acl
Create an access control rule
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
Google Calendar OAuth 2.0 tokens with scopes (calendar, calendar.events, calendar.readonly) are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw OAuth credentials and refresh tokens never enter the agent's context.
Intent-based discovery
Agents search by intent (e.g., 'schedule a meeting' or 'check calendar availability') and Jentic returns matching Calendar operations with their input schemas, required scopes, and recurrence rule format specifications, so the agent can execute scheduling operations without parsing Google's API documentation.
Time to first call
Direct Calendar integration: 2-4 days for OAuth setup, timezone handling, recurrence rule construction, and attendee management. Through Jentic: under 1 hour — search for the operation, load the schema, execute with auth handled automatically.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Calendar API through Jentic.
What authentication does the Google Calendar API use?
The Calendar API uses OAuth 2.0 with scopes including calendar.readonly for read-only access, calendar.events for event management, and calendar for full calendar control. Through Jentic, OAuth tokens are stored in the MAXsystem vault. The API supports both implicit and authorization code OAuth flows.
Can I check meeting availability across multiple people with the Calendar API?
Yes, the POST /freeBusy endpoint accepts a list of calendar IDs and a time range, returning busy intervals for each calendar. You can query up to 50 calendars in a single request with a time window up to 2 months. The response shows exactly which time slots are free across all participants.
What are the rate limits for the Google Calendar API?
The Calendar API allows 1,000,000 queries per day per project and enforces per-user rate limits of approximately 10 queries per second. Event creation and modification have stricter per-calendar limits. Batch requests can combine multiple operations to reduce quota consumption.
How do I create a recurring event with the Calendar API through Jentic?
Search Jentic for 'create recurring calendar event' to get the POST /calendars/{calendarId}/events schema. Set the recurrence field with an RRULE string like 'RRULE:FREQ=WEEKLY;BYDAY=MO,WE,FR' for specific days. Install Jentic with pip install jentic, authenticate at https://app.jentic.com/sign-up, and execute with the loaded schema.
Is the Google Calendar API free to use?
Yes, the Calendar API is free with no per-call charges. You need a Google Cloud project with the Calendar API enabled. Usage is governed by daily quota limits (1,000,000 queries/day per project) and per-user rate limits rather than pricing tiers.
Can I add a Google Meet link when creating an event?
Yes, include conferenceData in your event creation request with createRequest containing a requestId and conferenceSolutionKey of type 'hangoutsMeet'. Set conferenceDataVersion=1 as a query parameter on the POST /calendars/{calendarId}/events call. The response includes the generated Meet link in conferenceData.entryPoints.
How do I sync calendar changes to an external system?
Use POST /calendars/{calendarId}/events/watch with a webhook URL to receive push notifications on event changes. For initial sync, call GET /calendars/{calendarId}/events and store the nextSyncToken. On subsequent calls, pass syncToken to receive only incremental changes since the last sync.
GET STARTED