Complete the steps described in the rest of this page to create a simple Google Apps Script that makes requests to the Google Calendar API.
Prerequisites
To run this quickstart, you need the following prerequisites:
- A Google account with Google Calendar enabled.
- Access to Google Drive
Step 1: Create the script
- Create a new script by going to script.google.com/create.
- Replace the contents of the script editor with the following code:
New editor
- Click Save
.
- Click Untitled project at the top left, type Quickstart, and click Rename.
Legacy editor
- Click File > Save, name your project “Quickstart”, and click OK.
Step 2: Turn on the Google Calendar API
Enable the Calendar API advanced service in your script.
Step 3: Run the sample
New editor
In the Apps Script editor, click Run.
The first time you run the sample, it will prompt you to authorize access:
- Click Review permissions.
- Choose an account.
- Click Allow.
The script's execution log appears at the bottom of the window.
Legacy editor
In the Apps Script editor, click Run > listUpcomingEvents.
The first time you run the sample, it will prompt you to authorize access:
- Click the Continue button.
- Click the Accept button.
To view the script's output, click View > Logs.
Further reading
- Google Apps Script Advanced Services documentation
- Create events
- Calendar API reference documentation
Troubleshooting
This section describes some common issues that you may encounter while attempting to run this quickstart and suggests possible solutions.
ReferenceError: "[API NAME]" is not defined
This error occurs when the API hasn't been toggled on in the Apps Script code editor. Revisit Step 2.b and ensure the corresponding toggle is set to on.
This app isn't verified
If the OAuth consent screen displays the warning "This app isn't verified," your app is requesting scopes that provide access to sensitive user data. If your application uses sensitive scopes, your app must go through the verification process to remove that warning and other limitations. During the development phase, you can continue past this warning by selecting Advanced > Go to {Project Name} (unsafe).