Need help with google-api-nodejs-client?
Click the “chat” button below for chat support from the developer who created it, or find similar developers for support.

About the developer

9.6K Stars 1.7K Forks Apache License 2.0 4.0K Commits 71 Opened issues


Google's officially supported Node.js client library for accessing Google APIs. Support for authorization and authentication with OAuth 2.0, API Keys and JWT (Service Tokens) is included.

Services available


Need anything else?

Contributors list

Google Inc. logo

Google APIs Node.js Client

npm version Downloads Dependency Status Known Vulnerabilities

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

The full list of supported APIs can be found on the Google APIs Explorer. 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.

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

client libraries: single purpose idiomatic Node.js clients for Google Cloud Platform services.

Support and maintenance

These client libraries are officially 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


This library is distributed on

. In order to add it as a dependency, run the following command:
$ npm install googleapis

If you need to reduce startup times, you can also install a submodule as its own dependency. We make an effort to publish submodules that are not in this list. In order to add it as a dependency, run the following sample command, replacing with your preferred API:

$ npm install @googleapis/docs

You can run this search on npm, to find a list of the submodules available.

Using the client library

This is a very simple example. This creates a Blogger client and retrieves the details of a blog given the blog Id:

const {google} = require('googleapis');

// Each API may support multiple versions. With this sample, we're getting // v3 of the blogger API, and using an API key to authenticate. const blogger = google.blogger({ version: 'v3', auth: 'YOUR API KEY' });

const params = { blogId: '3213900' };

// get the blog details blogger.blogs.get(params, (err, res) => { if (err) { console.error(err); throw err; } console.log(The blog url is ${}); });

Instead of using callbacks you can also use promises!

  .then(res => {
    console.log(`The blog url is ${}`);
  .catch(error => {

Or async/await:

async function runSample() {
  const res = await blogger.blogs.get(params);
  console.log(`The blog url is ${}`);

You can also make calls directly to the APIs by installing a submodule:

const docs = require('@googleapis/docs')

const auth = new docs.auth.GoogleAuth({ keyFilename: 'PATH_TO_SERVICE_ACCOUNT_KEY.json', // Scopes can be specified either as an array or as a single, space-delimited string. scopes: [''] }); const authClient = await auth.getClient();

const client = await{ version: 'v1', auth: authClient });

const createResponse = await client.documents.create({ requestBody: { title: 'Your new document!', }, });



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.

API Reference

This library has a full set of API Reference Documentation. This documentation is auto-generated, and the location may change.

Authentication and authorization

There are multiple 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.

  • 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.

  • Application default credentials - Provides automatic access to Google APIs using the Google Cloud SDK for local development, or the GCE Metadata Server for applications deployed to Google Cloud Platform. Learn more.

  • Service account credentials - 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.

To learn more about the authentication client, see the Google Auth Library.

OAuth2 client

This module comes with an OAuth2 client that allows you to retrieve an access token, refresh it, 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

. You can find these pieces of information by going to the Developer Console, clicking your project --> APIs & auth --> credentials. - Navigate to the Cloud Console and Create a new OAuth2 Client Id - Select
Web Application
for the application type - Add an authorized redirect URI with the value
(or applicable value for your scenario) - Click
, and
on the following screen - Click the
icon next to your newly created OAuth2 Client Id

Make sure to store this file in safe place, and do not check this file into source control!

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


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} = require('googleapis');

const oauth2Client = new google.auth.OAuth2( YOUR_CLIENT_ID, YOUR_CLIENT_SECRET, YOUR_REDIRECT_URL );

// generate a url that asks permissions for Blogger and Google Calendar scopes const scopes = [ '', '' ];

const url = oauth2Client.generateAuthUrl({ // 'online' (default) or 'offline' (gets refresh_token) access_type: 'offline',

// If you only need one scope you can pass it as a string scope: scopes });


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 oauth2Client.getToken(code)

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

oauth2Client.on('tokens', (tokens) => {
  if (tokens.refresh_token) {
    // store the refresh_token in my database!

This tokens event only occurs in the first authorization, and you need to have set your

when calling the
method to receive the refresh token. If you have already given your app the requisiste permissions without setting the appropriate constraints for receiving a refresh token, you will need to re-authorize the application to receive a fresh refresh token. You can revoke your app's access to your account here.

To set the

at a later time, you can use the
  refresh_token: `STORED_REFRESH_TOKEN`

Once the client has a refresh token, access tokens will be acquired and refreshed automatically in the next call to the API.

Refresh tokens may stop working after they are granted, either because: - The user has revoked your app's access - The refresh token has not been used for 6 months - The user changed passwords and the refresh token contains Gmail scopes - The user account has exceeded a max number of live refresh tokens - The application has a status of 'Testing' and the consent screen is configured for an external user type, causing the token to expire in 7 days

As a developer, you should write your code to handle the case where a refresh token is no longer working.

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 Blogger API service to retrieve a blog's name, url, and its total amount of posts:

const {google} = require('googleapis');
const blogger = google.blogger_v3({
  version: 'v3',
  auth: 'YOUR_API_KEY' // specify your API key here

const params = { blogId: '3213900' };

async function main(params) { const res = await blogger.blogs.get({blogId: params.blogId}); console.log(${} has ${} posts! The blog url is ${}) };


To learn more about API keys, please see the documentation.

Application default credentials

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.

To use Application default credentials locally with the Google Cloud SDK, run:

$ gcloud auth application-default login

When running in GCP, service authorize is automatically provided via the GCE Metadata server.

const {google} = require('googleapis');
const compute = google.compute('v1');

async function main () { const auth = new google.auth.GoogleAuth({ // Scopes can be specified either as an array or as a single, space-delimited string. scopes: [''] }); const authClient = await auth.getClient();

// obtain the current project Id const project = await auth.getProjectId();

// Fetch the list of GCE zones within a project. const res = await compute.zones.list({ project, auth: authClient }); console.log(; }


Service account credentials

Service accounts allow you to perform server to server, app-level authentication using a robot account. You will create a service account, download a keyfile, and use that to authenticate to Google APIs. To create a service account: - Go to the Create Service Account Key page - Select

New Service Account
in the drop down - Click the

Save the service account credential file somewhere safe, and do not check this file into source control! To reference the service account credential file, you have a few options.

Using the
env var

You can start process with an environment variable named

. The value of this env var should be the full path to the service account credential file:
$ GOOGLE_APPLICATION_CREDENTIALS=./your-secret-key.json node server.js

Using the

Alternatively, you can specify the path to the service account credential file via the

property in the
const {google} = require('googleapis');

const auth = new google.auth.GoogleAuth({ keyFile: '/path/to/your-secret-key.json', scopes: [''], });

Setting global or service-level auth

You can set the

as a global or service-level option so you don't need to specify it every request. For example, you can set
as a global option:
const {google} = require('googleapis');

const oauth2Client = new google.auth.OAuth2( YOUR_CLIENT_ID, YOUR_CLIENT_SECRET, YOUR_REDIRECT_URL );

// set auth as a global default google.options({ auth: oauth2Client });

Instead of setting the option globally, you can also set the authentication client at the service-level:

const {google} = require('googleapis');
const oauth2Client = new google.auth.OAuth2(

const drive ={ version: 'v2', auth: oauth2Client });

See the Options section for more information.


Specifying request body

The body of the request is specified in the

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{
  userId: 'me',
  requestBody: {
    // Replace with `projects/${PROJECT_ID}/topics/${TOPIC_NAME}`
    topicName: `projects/el-gato/topics/gmail`

Media uploads

This client supports multipart media uploads. The resource parameters are specified in the

parameter object, and the media itself is specified in the
parameter with mime-type specified in

This example uploads a plain text file to Google Drive with the title "Test" and contents "Hello World".

const drive ={
  version: 'v3',
  auth: oauth2Client

const res = await drive.files.create({ requestBody: { name: 'Test', mimeType: 'text/plain' }, media: { mimeType: 'text/plain', body: 'Hello World' } });

You can also upload media by specifying

as a Readable stream. This can allow you to upload very large files that cannot fit into memory.
const fs = require('fs');

const drive ={ version: 'v3', auth: oauth2Client });

async function main() { const res = await drive.files.create({ requestBody: { name: 'testimage.png', mimeType: 'image/png' }, media: { mimeType: 'image/png', body: fs.createReadStream('awesome.png') } }); console.log(; }


For more examples of creation and modification requests with media attachments, take a look at the


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 'gaxios' object used in this library to make network calls to the API.

You may specify additional options either in the global

object or on a service client basis. The options you specify are attached to the
object so whatever
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

property of
will be set for every request:
const {google} = require('googleapis');
  // 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} = require('googleapis');
  // 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: '[email protected]'

Service-client options

You can also specify options when creating a service client.

const blogger = google.blogger({
  version: 'v3',
  // All requests made with this object will use the specified auth.
  auth: 'API KEY';

By doing this, every API call made with this service client will use

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.blogger({
  version: 'v3',
  // All requests made with this service client will contain the
  // blogId query parameter unless overridden in individual API calls.
  params: {
    blogId: '3213900'

// Calls with this drive client will NOT contain the blogId query parameter. const drive ='v3'); ...

Request-level options

You can specify an

object to be used per request. Each request also inherits the options specified at the service level and global level.

For example:

const {google} = require('googleapis');
const bigquery = google.bigquery('v2');

async function main() {

// This method looks for the GCLOUD_PROJECT and GOOGLE_APPLICATION_CREDENTIALS // environment variables. const auth = new google.auth.GoogleAuth({ scopes: [''] }); const authClient = await auth.getClient();

const projectId = await auth.getProjectId();

const request = { projectId, datasetId: '',

// This is a "request-level" option
auth: authClient


const res = await bigquery.datasets.delete(request); console.log(;



You can also override gaxios options per request, such as

, and

For example:

const res = await drive.files.export({
  fileId: 'asxKJod9s79', // A Google Doc
  mimeType: 'application/pdf'
}, {
  // Make sure we get the binary data
  responseType: 'stream'

Using a Proxy

You can use the following environment variables to proxy HTTP and HTTPS requests:


When HTTPPROXY / httpproxy are set, they will be used to proxy non-SSL requests that do not have an explicit proxy configuration option present. Similarly, HTTPSPROXY / httpsproxy 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 programmatically obtain the list of supported APIs, and all available versions:

const {google} = require('googleapis');
const apis = google.getSupportedAPIs();

This will return an object with the API name as object property names, and an array of version strings as the object values;


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

namespace. For example, the Drive v3 API types are all available from the
import {
  google,   // The top level object used to access services
  drive_v3, // For every service client, there is an exported namespace
  Auth,     // Namespace for auth related types
  Common,   // General types used throughout the library
} from 'googleapis';

// Note: using explicit types like Auth.GoogleAuth are only here for // demonstration purposes. Generally with TypeScript, these types would // be inferred. const auth: Auth.GoogleAuth = new google.auth.GoogleAuth(); const drive: drive_v3.Drive ={ version: 'v3', auth, });

// There are generated types for every set of request parameters const listParams: drive_v3.Params$Resource$Files$List = {}; const res = await drive.files.list(listParams);

// There are generated types for the response fields as well const listResults: drive_v3.Schema$FileList =;


This library has experimental support for HTTP/2. This support is experimental, and should not be used in production. To enable it for testing purposes, use the

option anywhere request parameters are accepted:
const {google} = require('googleapis');
  http2: true,

HTTP/2 is often more performant, as it allows multiplexing of multiple concurrent requests over a single socket. In a traditional HTTP/2 API, the client is directly responsible for opening and closing the sessions made to make requests. To maintain compatibility with the existing API, this module will automatically re-use existing sessions, which are collected after idling for 500ms. Much of the performance gains will be visible in batch style workloads, and tight loops. To provide feedback on the experimental API surface, please comment on this issue.

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

, see our Release Notes to learn about migrating your code from
. It's pretty easy :)


This library is licensed under Apache 2.0. Full license text is available in LICENSE.


We love contributions! Before submitting a Pull Request, it's always good to start with a new issue first. To learn more, see CONTRIBUTING.


We use cookies. If you continue to browse the site, you agree to the use of cookies. For more information on our use of cookies please see our Privacy Policy.