This document contains Google Calendar API-specific authorization and authentication information. Before reading this document, be sure to read the Google Workspace's general authentication and authorization information at Learn about authentication and authorization.
Configure OAuth 2.0 for authorization
Configure the OAuth consent screen and choose scopes to define what information is displayed to users and app reviewers, and register your app so that you can publish it later.
Calendar API scopes
To define the level of access granted to your app, you need to identify and declare authorization scopes. An authorization scope is an OAuth 2.0 URI string that contains the Google Workspace app name, what kind of data it accesses, and the level of access. Scopes are your app's requests to work with Google Workspace data, including users' Google Account data.
When your app is installed, a user is asked to validate the scopes used by the app. Generally, you should choose the most narrowly focused scope possible and avoid requesting scopes that your app doesn't require. Users more readily grant access to limited, clearly described scopes.
The Calendar API supports the following scopes:
| Scope | Meaning |
|---|---|
https://www.googleapis.com/auth/calendar |
See, edit, share, and permanently delete all the calendars you can access using Google Calendar. |
https://www.googleapis.com/auth/calendar.readonly |
See and download any calendar you can access using your Calendar. |
https://www.googleapis.com/auth/calendar.events |
View and edit events on all your calendars. |
https://www.googleapis.com/auth/calendar.events.readonly |
View events on all your calendars. |
https://www.googleapis.com/auth/calendar.settings.readonly |
View your Calendar settings. |
https://www.googleapis.com/auth/calendar.addons.execute |
Run as a Calendar add-on. |