Authorization
Stay organized with collections
Save and categorize content based on your preferences.
Every request your application sends to the AdMob API must include an authorization token. The token also identifies your application to Google.
About authorization protocols
Your application must use OAuth 2.0 to authorize requests. No other authorization protocols are supported. If your application uses Sign In With Google, some aspects of authorization are handled for you.
Authorizing requests with OAuth 2.0
All requests to the AdMob API must be authorized by an authenticated user.
This process is facilitated with an OAuth client ID.
Get an OAuth client ID
Or create one in the Credentials page.
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:
- When your application needs access to user data, it asks Google for a particular scope of access.
- Google displays a consent screen to the user, asking them to authorize your application to request some of their data.
- If the user approves, then Google gives your application a short-lived access token.
- Your application requests user data, attaching the access token to the request.
- 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 AdMob API:
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.
|
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).
Tip: The Google APIs client libraries can handle some of the authorization process for you. They are available for a variety of programming languages; check the page with libraries and samples for more details.
Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2025-08-20 UTC.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-20 UTC."],[[["\u003cp\u003eEvery AdMob API request requires an authorization token for application identification and user data access.\u003c/p\u003e\n"],["\u003cp\u003eAdMob API exclusively supports OAuth 2.0 for authorization, requiring applications to obtain user consent and access tokens.\u003c/p\u003e\n"],["\u003cp\u003eApplications need an OAuth client ID and specific scopes to request access to AdMob data like account information or reports.\u003c/p\u003e\n"],["\u003cp\u003eGoogle provides client libraries to simplify the authorization process across various programming languages.\u003c/p\u003e\n"]]],["All AdMob API requests require an OAuth 2.0 authorization token, obtainable via an OAuth client ID. The application requests a specific access scope, which prompts Google to display a consent screen to the user. Upon approval, Google grants a short-lived access token. The application then uses this token to request data. Access scopes include `admob.readonly` for general data and `admob.report` for performance reports. Google APIs client libraries can help manage parts of the process.\n"],null,["Every request your application sends to the AdMob API must include an authorization token. The token also identifies your application to Google.\n\nAbout authorization protocols\n\nYour application must use [OAuth 2.0](https://developers.google.com/identity/protocols/OAuth2) to authorize requests. No other authorization protocols are supported. If your application uses [Sign In With Google](https://developers.google.com/identity/gsi/web), some aspects of authorization are handled for you.\n\nAuthorizing requests with OAuth 2.0\n\nAll requests to the AdMob API must be authorized by an authenticated user.\n\nThis process is facilitated with an OAuth client ID.\nGet an OAuth client ID\n\nOr create one in the [Credentials page](https://console.cloud.google.com/apis/credentials).\n\nThe 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:\n\n1. When your application needs access to user data, it asks Google for a particular **scope** of access.\n2. Google displays a **consent screen** to the user, asking them to authorize your application to request some of their data.\n3. If the user approves, then Google gives your application a short-lived **access token**.\n4. Your application requests user data, attaching the access token to the request.\n5. If Google determines that your request and the token are valid, it returns the requested data.\n\nSome 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](https://developers.google.com/identity/protocols/OAuth2).\n\nHere's the OAuth 2.0 scope information for the AdMob API:\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\nTo request access using OAuth 2.0, your application needs the scope information, as well as\ninformation that Google supplies when you register your application (such as the client ID and the\nclient secret).\n\n**Tip:** The Google APIs client libraries can handle some of the authorization process for you. They are available for a variety of programming languages; check the [page with libraries and samples](/admob/api/v1/libraries) for more details."]]