Google Calendar APIConnect Google Calendar without building on its API
Google Calendar has a REST API. Self-serve for any developer via a Google Cloud project with the Calendar API enabled. If you're reading the docs because you need Google Calendar 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 Google Calendar and your other tools.
- APIREST (JSON)
- AuthOAuth 2.0
- AccessSelf-serve
What the Google Calendar API gives you
- Type
- REST (JSON)
- Authentication
- OAuth 2.0
- Who can get access
- Self-serve for any developer via a Google Cloud project with the Calendar API enabled.
- What it covers
- Events, calendars, calendar list, user settings, and ACL (sharing) rules.
- Limits
- 10,000 requests/minute per project and 600 requests/minute per user per project, with a 1,000,000 requests/day per-project billing threshold.
Official docs: developers.google.com. Checked September 2026. Vendors change access terms, so confirm with Google Calendar before you build.
Building on the Google Calendar API vs. having Caddi run it
| The job | Build it on the API | With Caddi |
|---|---|---|
| Getting access | Register an app, get Google Calendar credentials, and manage tokens and refreshes. | Connect your Google Calendar 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 Google Calendar 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 Google Calendar work off someone's desk, the build is the slow part.
What teams usually want the Google Calendar API for
Pre-meeting prep packet
Caddi reads the day's calendar, matches each meeting to a CRM record, and emails the host a prep packet with key context.
Time-entry drafts
Caddi turns yesterday's calendar into a draft set of billable time entries against the right matters, queued for review.
Follow-up tasks from events
Once a meeting ends, Caddi opens the right follow-up tasks in your project or matter system and notifies the attendee.
Google Calendar API questions
Does Google Calendar have an API?
Yes. Google Calendar has a REST API, authenticated with OAuth 2.0. The official documentation is at https://developers.google.com/workspace/calendar/api/guides/overview.
How do I get access to the Google Calendar API?
Self-serve for any developer via a Google Cloud project with the Calendar API enabled.
Does the Google Calendar API have rate limits?
10,000 requests/minute per project and 600 requests/minute per user per project, with a 1,000,000 requests/day per-project billing threshold.
Can I connect Google Calendar to my other tools without writing code against its API?
Yes. With Caddi you show the Google Calendar task once, the way you'd train a new hire, and Caddi builds it as verified code that runs across Google Calendar 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 Google Calendar with Caddi?
No. There is no integration code for you to write or maintain. Every automation Caddi builds for Google Calendar is reviewed before it runs in production, and every run is logged.
Connect Google Calendar without the build.
Drop your work email and pick a time. We'll show you Caddi running your Google Calendar workflow end to end.