Stay organized with collections
Save and categorize content based on your preferences.
All Google AdMob API calls must be authorized through
OAuth2 so your app can interact with web services
on the user's behalf. OAuth2 enables your AdMob API client app to access a
user's AdMob account without having to handle or store the user's username or
password. For an overview of authorization, see
Authorization.
Perform the following steps to generate the OAuth2 credentials and make your
first request.
Check the table below to see which authentication type is most appropriate
for your app:
Choose your OAuth2 authentication type
If ...
Desktop app
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 only authenticates 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.
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.
Enabling the API for an existing project
The following steps apply to users who have an existing project and prefer to
activate the AdMob API for it manually.
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.
Set your user type to External and publishing status to
Published.
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.
Select Desktop app or Web Application as the application type, give
it a name, then click Create.
When done, you are presented with an OAuth 2.0 client ID and client secret,
which you can download in JSON format and save for later use.
Make a request
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.
With OAuth 2.0 credentials created, you're ready to start using
the AdMob API. To request access using OAuth 2.0, your app also needs 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.
https://www.googleapis.com/auth/admob.report
See ad performance and earnings reports. See publisher ID,
timezone, and default currency code.
Make your first request to generate a report using examples in
Java,
PHP,
Python or
curl.
[null,null,["Last updated 2025-08-28 UTC."],[[["\u003cp\u003eAll Google AdMob API calls require OAuth2 authorization for your app to access user data securely without storing sensitive login credentials.\u003c/p\u003e\n"],["\u003cp\u003eChoose between desktop or web app authentication flow based on your app's needs and authorization process.\u003c/p\u003e\n"],["\u003cp\u003eCreate or select a Google API project and enable the AdMob API before generating OAuth2 credentials.\u003c/p\u003e\n"],["\u003cp\u003eMake authorized requests to the AdMob API using HTTP clients or client libraries in various programming languages.\u003c/p\u003e\n"],["\u003cp\u003eRevoke access tokens through your Google account permissions or the Google Identity API when necessary.\u003c/p\u003e\n"]]],["To use the Google AdMob API, authorize calls via OAuth2. First, create or select a project in the Google API Console and enable the AdMob API. Next, create OAuth2 credentials, choosing between \"Desktop app\" or \"Web app\" authentication types based on your needs. Configure the OAuth consent screen, download the generated client ID and secret, and then use these credentials to authorize requests with specified scopes, such as `admob.monetization` or `admob.readonly`. To start making requests, you can utilize the Google API client libraries. If you want to revoke access, you can do so from your Google account or using Google Identity API.\n"],null,["All Google AdMob API calls must be authorized through\n[OAuth2](/identity/protocols/oauth2) so your app can interact with web services\non the user's behalf. OAuth2 enables your AdMob API client app to access a\nuser's AdMob account without having to handle or store the user's username or\npassword. For an overview of authorization, see\n[Authorization](/admob/api/v1/how-tos/authorizing).\n\nPerform the following steps to generate the OAuth2 credentials and make your\nfirst request.\n\nPrerequisites\n\n- A [Google Account](//google.com/accounts/NewAccount).\n\n- A [Google AdMob account](//admob.google.com/home/get-started).\n\n- Familiarity with [REST basics](/admob/api/v1/prereqs#rest) and [authorizing requests with\n OAuth 2.0](/admob/api/v1/how-tos/authorizing).\n\nDetermine your authentication type\n\nCheck the table below to see which **authentication type** is most appropriate\nfor your app:\n\n| Choose your OAuth2 authentication type | If ... |\n|----------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| **Desktop app** | - 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 only authenticates Google AdMob users from one machine. |\n| **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. |\n\n| **Key Point:** You can still choose the desktop app flow even if you're developing an app to run on a server. The difference is whether the OAuth authorization is completed locally or remotely. A desktop flow requires authorization to be completed on the local machine, whereas the web-flow lets authorization be completed on Google's authorization server.\n\nCreate a project\n\nTo get started using the AdMob API, you need to first create or select a\nproject in the Google API Console and enable the API using [the setup\ntool](https://console.cloud.google.com/start/api?id=admob.googleapis.com&credential=client_key),\nwhich guides you through the process and activates the AdMob API\nautomatically. \n\nEnabling the API for an existing project\n\nThe following steps apply to users who have an existing project and prefer to\nactivate the AdMob API for it manually.\n\nTo enable an API for your project:\n\n1. [Open the API Library](https://console.developers.google.com/apis/library) in the Google API Console.\n2. If prompted, select a project, or create a new one. The API Library lists all available APIs, grouped by product family and popularity.\n3. If the API you want to enable isn't visible in the list, use search to find it, or click **View All** in the product family it belongs to.\n4. Select the API you want to enable, then click the **Enable** button.\n5. If prompted, enable billing.\n6. If prompted, read and accept the API's Terms of Service.\n\nCreate OAuth2 credentials\n\nThe following instructions guide you through the process of creating an OAuth\n2.0 client ID to use with the [installed app\nflow](/identity/protocols/OAuth2InstalledApp).\n\n1. Go to the [Clients page](https://console.developers.google.com/auth/clients).\n2. Click **CREATE CREDENTIALS \\\u003e OAuth client ID**.\n\n If you hadn't configured an OAuth consent screen for this project\n previously, you'll be directed to do so now. Click **CONFIGURE CONSENT\n SCREEN**. There are multiple ways to configure your consent screen to\n use your OAuth 2.0 client ID.\n 1. Set your user type to **External** and publishing status to **Published**.\n 2. Or, set your user type to **External** and publishing status to\n **Testing** , then add **Test users** by selecting **add users** to\n give them access to use your OAuth 2.0 client ID.\n\n See additional information on [setting up your OAuth consent\n screen](//support.google.com/cloud/answer/10311615).\n3. Select **Desktop app** or **Web Application** as the application type, give\n it a name, then click **Create**.\n\nWhen done, you are presented with an OAuth 2.0 client ID and client secret,\nwhich you can download in JSON format and save for later use.\n\nMake a request\n\nThe AdMob API is built on HTTP and JSON, so any standard HTTP client can send\nrequests to it and parse the responses. However, the [Google API client\nlibraries](/admob/api/v1/libraries) provide better language integration,\nimproved security, and support for making authorized requests. The client\nlibraries are available in a number of programming languages; by using them you\ncan avoid the need to manually set up HTTP requests and parse the responses.\n| **Note:** The first time you activate the OAuth flow, you are asked to provide your AdMob publisher ID and accept an authorization prompt in your browser. Before accepting, make sure you're signed in with a Google Account that has access to your AdMob account. Your app is then authorized to access data on behalf of whichever account is currently logged in.\n\nWith [OAuth 2.0 credentials created](#credentials), you're ready to start using\nthe AdMob API. To request access using OAuth 2.0, your app also needs scope\ninformation:\n\n\n| Scope | Meaning |\n|--------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| `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. |\n| `https://www.googleapis.com/auth/admob.report` | See ad performance and earnings reports. See publisher ID, timezone, and default currency code. |\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\nMake your first request to generate a report using examples in\n[Java](/admob/api/v1/reporting#java-client-library),\n[PHP](/admob/api/v1/reporting#php-client-library),\n[Python](/admob/api/v1/reporting#python-client-library) or\n[curl](/admob/api/v1/reporting#curl-command-line).\n\nRevoke shared tokens\n\nYou can revoke shared tokens in two ways:\n\n1. Navigate to your [Google account\n permissions page](//myaccount.google.com/permissions) and revoke access from\n the relevant project.\n\n2. Alternatively, you can revoke web application tokens using the [Google\n Identity API](/identity/protocols/oauth2/web-server#tokenrevoke)."]]
