Authorize Requests

When your application requests private user data, the request must be authorized by an authenticated user who has access to that data. This is called user-centric OAuth flow. If your application doesn't need to access user data, then you should use a server-centric OAuth flow based on a service account. For more information about these two OAuth flows and authentication in general, see Google Cloud Storage Authentication. This page describes the different type of credentials you can create and use with Google Cloud Storage for both user-centric flows and server-centric oauth flows.

Identifying your application

Every request your application sends to the Google Cloud Storage JSON API needs to identify your application to Google. There are two ways to identify your application: using an OAuth 2.0 token (which also authorizes the request) and/or using the application's API key. Here's how to determine which of those options to use:

  • If the request requires authorization (such as a request for an individual's private data), then the application must provide an OAuth 2.0 token with the request. The application may also provide the API key, but it doesn't have to.
  • If the request doesn't require authorization (such as a request for public data), then the application must provide either the API key or an OAuth 2.0 token, or both—whatever option is most convenient for you.

About authorization protocols

Your application must use OAuth 2.0 to authorize requests. No other authorization protocols are supported. If your application uses Google Sign-In, some aspects of authorization are handled for you.

Authorizing requests with OAuth 2.0

Requests to the Google Cloud Storage JSON API for non-public user data must be authorized by an authenticated user.

The details of the authorization process, or "flow," for OAuth 2.0 vary somewhat depending on what kind of application you're writing. The following general process applies to all application types:

  1. When you create your application, you register it using the Google Cloud Platform Console. Google then provides information you'll need later, such as a client ID and a client secret.
  2. Activate the Google Cloud Storage JSON API in the Google Cloud Platform Console. (If the API isn't listed in the Cloud Platform Console, then skip this step.)
  3. When your application needs access to user data, it asks Google for a particular scope of access.
  4. Google displays a consent screen to the user, asking them to authorize your application to request some of their data.
  5. If the user approves, then Google gives your application a short-lived access token.
  6. Your application requests user data, attaching the access token to the request.
  7. If Google determines that your request and the token are valid, it returns the requested data.

Some flows include additional steps, such as using refresh tokens to acquire new access tokens. For detailed information about flows for various types of applications, see Google's OAuth 2.0 documentation.

Here's the OAuth 2.0 scope information for the Google Cloud Storage JSON API:

Scope Meaning
https://www.googleapis.com/auth/devstorage.full_control Read/write and ACL management access to Google Cloud Storage.
https://www.googleapis.com/auth/devstorage.read_write Read/write access to Google Cloud Storage.
https://www.googleapis.com/auth/devstorage.read_only Read-only access to Google Cloud Storage.

To request access using OAuth 2.0, your application needs the scope information, as well as information that Google supplies when you register your application (such as the client ID and the client secret).

Acquiring and using an API key

Requests to the Google Cloud Storage JSON API for public data must be accompanied by an identifier, which can be an API key or an access token.

To acquire an API key:

  1. Open the Credentials page in the Cloud Platform Console.
  2. This API supports two types of credentials. Create whichever credentials are appropriate for your project:
    • OAuth 2.0: Whenever your application requests private user data, it must send an OAuth 2.0 token along with the request. Your application first sends a client ID and, possibly, a client secret to obtain a token. You can generate OAuth 2.0 credentials for web applications, service accounts, or installed applications.

      For more information, see the OAuth 2.0 documentation.

    • API keys: A request that does not provide an OAuth 2.0 token must send an API key. The key identifies your project and provides API access, quota, and reports.

      The API supports several types of API keys. If the key type that you need doesn't already exist, then create an API key in the Console by clicking Create credentials > API key and selecting the appropriate key type. Then enter the additional data for that key type.

To keep your API keys secure, follow the best practices for securely using API keys.

After you have an API key, your application can append the query parameter key=yourAPIKey to all request URLs.

The API key is safe for embedding in URLs; it doesn't need any encoding.

Send feedback about...

Cloud Storage Documentation