OAuth setup

All Google AdMob API calls must be authorized through OAuth2, so the application can interact with web services on the user's behalf. OAuth2 enables your AdMob API client application to access a user's AdMob account without having to handle or store the user's username or password. For a brief overview of authorization, read about how to authorize and identify your app to Google.

Generate tokens and make a request

Perform the following steps to generate the OAuth2 credentials and make your first request.

1. Determine your authentication type

Check the table below to see which authentication type is most appropriate for your AdMob API application:

Choose your OAuth2 authentication type If ...
Desktop app (recommended)
  • You're managing all of your AdMob API accounts using a single top level manager account.
  • You're a first-time user, or want to get started quickly with the simplest setup.
  • Your app will only authenticate Google AdMob users from one machine.
Web app
  • You want to authenticate as a user who can grant permission to your app to access their AdMob API account data.
  • You want to easily generate multiple authorization credentials, to manage third-party accounts for example.
  • Your app requires callback URLs. Callback URLs are not supported in the desktop app flow.

2. Create a project

To get started using the AdMob API, you need to first create or select a project in the Google API Console and enable the API using the setup tool, which guides you through the process and activates the AdMob API automatically.

3. Create OAuth2 credentials

The following instructions guide you through the process of creating an OAuth 2.0 client ID to use with the installed app flow.

  1. Go to the Credentials page.
  2. Click CREATE CREDENTIALS > OAuth client ID.

    1. If you hadn't configured an OAuth consent screen for this project previously, you'll be directed to do so now. Click CONFIGURE CONSENT SCREEN. There are multiple ways to configure your consent screen to use your OAuth 2.0 client ID.

      1. Set your user type to External and publishing status to Published.
      2. Or, set your user type to External and publishing status to Testing, then add Test users by selecting add users to give them access to use your OAuth 2.0 client ID.

      See additional information on setting up your OAuth consent screen.

  3. Select Desktop app or Web Application as the application type, give it a name, then click Create.

When done, you'll be presented with an OAuth 2.0 client ID and client secret, which you can download in JSON format and save for later use.

4. Configure and use a client library

The AdMob API is built on HTTP and JSON, so any standard HTTP client can send requests to it and parse the responses. However, the Google API client libraries provide better language integration, improved security, and support for making authorized requests. The client libraries are available in a number of programming languages; by using them you can avoid the need to manually set up HTTP requests and parse the responses.

Make your first request to generate a report using examples in Java, PHP, Python or curl.

With OAuth 2.0 credentials created, you're ready to start using the AdMob API. To request access using OAuth 2.0, your application will also need the scope information.

Here's the OAuth 2.0 scope information:

Scope Meaning
https://www.googleapis.com/auth/admob.readonly See all AdMob data. This may include account information, inventory and mediation settings, reports, and other data. This doesn't include sensitive data, such as payments or campaign details.

Revoke shared tokens

You can revoke shared tokens in two ways:

  1. Navigate to your Google account permissions page and revoke access from the relevant project.

  2. Alternatively, you can revoke web application tokens using the Google Identity API.