Google Calendar API Documentation
This is the complete API documentation for connecting to the Google Calendar API using MindCloud's Universal API. If you are new to MindCloud, start with the Introduction to see how one API can sit in front of many different apps.
MindCloud is an integration company that offers one normalized API to access 3,100+ apps from a single place. It cleans up provider-specific quirks, keeps requests and responses consistent, and centralizes authentication so you do not need to manage separate flows for every app. Browse other apps.
Meet Google Calendar: Schedule events, share calendars, book time, and coordinate meetings. Keep reading to get started.
Quickstart
Before you run your first Google Calendar request, you need three things:
- A MindCloud account — sign in or create an account at MindCloud.
- A MindCloud API Key — create one in API Keys. Keep it on your server.
- At least one Google Calendar connection — create or choose one in Connections. Note its
connectionId.
Every Google Calendar action uses the same URL pattern:
https://connect.mindcloud.co/v1/universal/googleCalendar/latest/actions/{actionSlug}You need a MindCloud API Key and a Google Calendar connection. Then call an action such as Get ACL Rule:
curl --request GET \
--url "https://connect.mindcloud.co/v1/universal/googleCalendar/latest/actions/get-acl-rule" \
--header "Authorization: Bearer $MINDCLOUD_API_KEY" \
--get \
--data-urlencode "connectionId=$CONNECTION_ID"Every response comes back in the same envelope, with your rows in a data array:
{
"success": true,
"data": [
{ "id": "1042", "name": "Ava" }
],
"meta": {}
}After your first request works, use Shape your requests to control arguments, pagination, filtering, fields, and errors.
Authentication
Authentication has two layers. Your MindCloud API Key authenticates the request to MindCloud, sent as a Bearer token in the Authorization header. The connectionId selects the connected Google Calendar account that should run the action. MindCloud stores and refreshes the Google Calendar credentials behind that connection, so you never send provider tokens with your requests.
Pass connectionId in the query string for GET and DELETE actions, and in the JSON body for POST, PUT, and PATCH actions. Keep your MindCloud API Key on your server; do not ship it in browser code, mobile apps, public repositories, or logs.
Google Calendar actions
All 27 published actions for this Google Calendar version. Each page documents the endpoint, arguments, and response controls.
- POSTAdd Calendar to List
- DELETEClear Calendar
- POSTCreate ACL Rule
- POSTCreate Calendar
- POSTCreate Event
- DELETEDelete ACL Rule
- DELETEDelete Event
- GETGet ACL Rule
- GETGet Calendar List Entry
- GETGet Calendar Metadata
- GETGet Colors
- GETGet Event
- GETGet Setting
- POSTImport Event
- GETList ACL Rules
- GETList Calendars
- GETList Event Instances
- GETList Events
- GETList Settings
- PUTMove Event
- PUTPatch Calendar List Entry
- GETQuery Free/Busy
- POSTQuick Add Event
- DELETERemove Calendar from List
- PUTUpdate ACL Rule
- PUTUpdate Calendar List Entry
- PUTUpdate Event
Related apps
More Productivity apps on the Universal API, behind the same REST shape. Or browse all apps.