Google APIs Node.js Client
Node.js client library for using Google APIs. Support for authorization and authentication with OAuth 2.0, API Keys and JWT tokens is included.
- Google APIs
- Getting started
- Authentication and authorization
- Usage
- License
- Contributing
- Questions/problems?
Google APIs
The full list of supported APIs can be found here. The API endpoints are automatically generated, so if the API is not in the list, it is currently not supported by this API client library.
Supported APIs are listed on the Google APIs Explorer.
Working with Google Cloud Platform APIs?
If you're working with Google Cloud Platform APIs such as Datastore, Cloud Storage or Pub/Sub, consider using the @google-cloud
client libraries: single purpose idiomatic Node.js clients for Google Cloud Platform services.
Support and maintenance
These client libraries are official supported by Google. However, these libraries are considered complete and are in maintenance mode. This means that we will address critical bugs and security issues but will not add any new features. For Google Cloud Platform APIs, we recommend using google-cloud-node which is under active development.
This library supports the maintenance LTS, active LTS, and current release of node.js. See the node.js release schedule for more information.
Getting started
Installation
This library is distributed on npm
. In order to add it as a dependency, run the following command:
$ npm install googleapis
First example
This is a very simple example. This creates a Blogger client and retrieves the details of a blog given the blog Id:
const google = ;// Each API may support multiple version. With this sample, we're getting// v3 of the blogger API, and using an API key to authenticate.const blogger = google;const params =blogId: 3213900;// get the blog detailsbloggerblogs;
Instead of using callbacks you can also use promises!
bloggerblogs;
Or async/await:
{const res = await bloggerblogs;console;};
Samples
There are a lot of samples 🤗 If you're trying to figure out how to use an API ... look there first! If there's a sample you need missing, feel free to file an issue.
Authentication and authorization
The are three primary ways to authenticate to Google APIs. Some service support all authentication methods, other may only support one or two.
-
OAuth2 - This allows you to make API calls on behalf of a given user. In this model, the user visits your application, signs in with their Google account, and provides your application with authorization against a set of scopes. Learn more.
-
Service <--> Service - In this model, your application talks directly to Google APIs using a Service Account. It's useful when you have a backend application that will talk directly to Google APIs from the backend. Learn more.
-
API Key - With an API key, you can access your service from a client or the server. Typically less secure, this is only available on a small subset of services with limited scopes. Learn more.
To learn more about the authentication client, see the Google Auth Library.
OAuth2 client
This client comes with an OAuth2 client that allows you to retrieve an access token and refreshes the token and retry the request seamlessly The basics of Google's OAuth2 implementation is explained on Google Authorization and Authentication documentation.
In the following examples, you may need a CLIENT_ID
, CLIENT_SECRET
and REDIRECT_URL
. You can find these pieces of information by going to the Developer Console, clicking your project --> APIs & auth --> credentials.
For more information about OAuth2 and how it works, see here.
A complete sample application that authorizes and authenticates with the OAuth2 client is available at samples/oauth2.js
.
Generating an authentication URL
To ask for permissions from a user to retrieve an access token, you redirect them to a consent page. To create a consent page URL:
const google = ;const oauth2Client =YOUR_CLIENT_IDYOUR_CLIENT_SECRETYOUR_REDIRECT_URL;// generate a url that asks permissions for Google+ and Google Calendar scopesconst scopes ='https://www.googleapis.com/auth/plus.me''https://www.googleapis.com/auth/calendar';const url = oauth2Client;
IMPORTANT NOTE - The refresh_token
is only returned on the first authorization. More details here.
Retrieve authorization code
Once a user has given permissions on the consent page, Google will redirect the page to the redirect URL you have provided with a code query parameter.
GET /oauthcallback?code={authorizationCode}
Retrieve access token
With the code returned, you can ask for an access token as shown below:
// This will provide an object with the access_token and refresh_token.// Save these somewhere safe so they can be used at a later time.const tokens = await oauth2Clientoauth2Client;
With the credentials set on your OAuth2 client - you're ready to go!
Handling refresh tokens
Access tokens expire. This library will automatically use a refresh token to obtain a new access token if it is about to expire. An easy way to make sure you always store the most recent tokens is to use the tokens
event:
oauth2client;
To set the refresh_token
at a later time, you can use the setCredentials
method:
oauth2client;
Once the client has a refresh token, access tokens will be acquired and refreshed automatically in the next call to the API.
Using API keys
You may need to send an API key with the request you are going to make. The following uses an API key to make a request to the Google+ API service to retrieve a person's profile given a userId:
const google = ;const plus = google;{const res = await pluspeople;console;};;
To learn more about API keys, please see the documentation.
Service to Service Authentication
Rather than manually creating an OAuth2 client, JWT client, or Compute client, the auth library can create the correct credential type for you, depending upon the environment your code is running under.
For example, a JWT auth client will be created when your code is running on your local developer machine, and a Compute client will be created when the same code is running on a configured instance of Google Compute Engine.
The code below shows how to retrieve a default credential type, depending upon the runtime environment. The createScopedRequired must be called to determine when you need to pass in the scopes manually, and when they have been set for you automatically based on the configured runtime environment.
{ // This method looks for the GCLOUD_PROJECT and GOOGLE_APPLICATION_CREDENTIALS // environment variables. const auth = await googleauth; // obtain the current project Id const project = await googleauth; // Fetch the list of GCE zones within a project. const res = await computezones; console;} ;
Setting global or service-level auth
You can set the auth
as a global or service-level option so you don't need to specify it every request. For example, you can set auth
as a global option:
const google = ;const oauth2Client =YOUR_CLIENT_IDYOUR_CLIENT_SECRETYOUR_REDIRECT_URL;// set auth as a global defaultgoogleoptionsauth: oauth2Client;
Instead of setting the option globally, you can also set the authentication client at the service-level:
const google = ;const oauth2Client =YOUR_CLIENT_IDYOUR_CLIENT_SECRETYOUR_REDIRECT_URL;const drive = google;
See the Options section for more information.
Usage
Specifying request body
The body of the request is specified in the requestBody
parameter object of the request. The body is specified as a JavaScript object with key/value pairs. For example, this sample creates a watcher that posts notifications to a Google Cloud Pub/Sub topic when emails are sent to a gmail account:
const res = await gmailusers;console;
Media uploads
This client supports multipart media uploads. The resource parameters are specified in the requestBody
parameter object, and the media itself is specified in the media.body
parameter with mime-type specified in media.mimeType
.
This example uploads a plain text file to Google Drive with the title "Test" and contents "Hello World".
const drive = google;const res = await drivefiles;
You can also upload media by specifying media.body
as a Readable stream. This can allow you to upload very large files that cannot fit into memory.
const fs = ; const drive = google; { const res = await drivefiles; console;} ;
For more examples of creation and modification requests with media attachments, take a look at the samples/drive/upload.js
sample.
Request Options
For more fine-tuned control over how your API calls are made, we provide you with the ability to specify additional options that can be applied directly to the 'axios' object used in this library to make network calls to the API.
You may specify additional options either in the global google
object or on a service client basis. The options you specify are attached to the axios
object so whatever axios
supports, this library supports. You may also specify global or per-service request parameters that will be attached to all API calls you make.
A full list of supported options can be found here.
Global options
You can choose default options that will be sent with each request. These options will be used for every service instantiated by the google client. In this example, the timeout
property of AxiosRequestConfig
will be set for every request:
const google = ;googleoptions // All requests made with this object will use these settings unless overridden. timeout: 1000 auth: auth;
You can also modify the parameters sent with each request:
const google = ;googleoptions // All requests from all services will contain the above query parameter // unless overridden either in a service client or in individual API calls. params: quotaUser: 'user123@example.com' ;
Service-client options
You can also specify options when creating a service client.
const blogger = google;
By doing this, every API call made with this service client will use 'API KEY'
to authenticate.
Note: Created clients are immutable so you must create a new one if you want to specify different options.
Similar to the examples above, you can also modify the parameters used for every call of a given service:
const blogger = google; // Calls with this drive client will NOT contain the blogId query parameter.const drive = google;...
Request-level options
You can specify an auth
object to be used per request. Each request also inherits the options specified at the service level and global level.
For example:
const google = ;const bigquery = google; { // This method looks for the GCLOUD_PROJECT and GOOGLE_APPLICATION_CREDENTIALS // environment variables. const client = await googleauth; const projectId = await googleauth; const request = projectId datasetId: '<YOUR_DATASET_ID>' // This is a "request-level" option auth: client ; const res = await bigquerydatasets; console; } ;
You can also override axios options per request, such as url
, method
, and encoding
.
For example:
const res = await drivefiles;
Using a Proxy
You can use the following environment variables to proxy HTTP and HTTPS requests:
HTTP_PROXY
/http_proxy
HTTPS_PROXY
/https_proxy
When HTTP_PROXY / http_proxy are set, they will be used to proxy non-SSL requests that do not have an explicit proxy configuration option present. Similarly, HTTPS_PROXY / https_proxy will be respected for SSL requests that do not have an explicit proxy configuration option. It is valid to define a proxy in one of the environment variables, but then override it for a specific request, using the proxy configuration option.
Getting Supported APIs
You can programatically obtain the list of supported APIs, and all available versions:
const google = ;const apis = google;
This will return an object with the API name as object property names, and an array of version strings as the object values;
TypeScript
This library is written in TypeScript, and provides types out of the box. All classes and interfaces generated for each API are exported under the ${apiName}_${version}
namespace. For example, the Drive v3 API types are are all available from the drive_v3
namespace:
;
Release Notes & Breaking Changes
You can find a detailed list of breaking changes and new features in our Release Notes. If you've used this library before 25.x
, see our Release Notes to learn about migrating your code from 24.x.x
to 25.x.x
. It's pretty easy :)
License
This library is licensed under Apache 2.0. Full license text is available in COPYING.
Contributing
We love contributions! Before submitting a Pull Request, it's always good to start with a new issue first. To learn more, see CONTRIBUTING.
Questions/problems?
- Ask your development related questions on Stackoverflow.
- If you've found an bug/issue, please file it on GitHub.