Complete the steps described in the rest of this page to create a simple Go command-line application that makes requests to the Google Calendar API.
Prerequisites
To run this quickstart, you need the following prerequisites:
- Go, latest version recommended.
- Git, latest version recommended.
- A Google account with Google Calendar enabled
Step 1: Turn on the Google Calendar API
Click this button to create a new Cloud Platform project and automatically enable the Google Calendar API:
Enable the Google Calendar API
In resulting dialog click DOWNLOAD CLIENT CONFIGURATION and save the filecredentials.json
to your working directory.
Step 2: Prepare the workspace
- Set the
GOPATH
environment variable to your working directory. - Get the Google Calendar API Go client library and OAuth2 package using the following commands:
go get -u google.golang.org/api/calendar/v3
go get -u golang.org/x/oauth2/google
Step 3: Set up the sample
Create a file named quickstart.go
in your working directory and copy
in the following code:
Step 4: Run the sample
Build and run the sample using the following command from your working directory:
go run quickstart.go
The first time you run the sample, it will prompt you to authorize access:
Browse to the provided URL in your web browser.
If you are not already logged into your Google account, you will be prompted to log in. If you are logged into multiple Google accounts, you will be asked to select one account to use for the authorization.
- Click the Accept button.
- Copy the code you're given, paste it into the command-line prompt, and press Enter.
Notes
- Authorization information is stored on the file system, so subsequent executions will not prompt for authorization.
- The authorization flow in this example is designed for a command-line application. For information on how to perform authorization in a web application, see Using OAuth 2.0 for Web Server Applications.
Further reading
- Google Developers Console help documentation
- Google APIs Client for Go
- 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.
This app isn't verified.
The OAuth consent screen that is presented to the user may show the warning "This app isn't verified" if it is requesting scopes that provide access to sensitive user data. These applications must eventually go through the verification process to remove that warning and other limitations. During the development phase you can continue past this warning by clicking Advanced > Go to {Project Name} (unsafe).