授權
透過集合功能整理內容
你可以依據偏好儲存及分類內容。
您的應用程式傳送至 AdMob API 的每項要求都必須包含授權權杖。這個權杖也可讓 Google 識別您的應用程式。
關於授權通訊協定
您的應用程式必須使用 OAuth 2.0 對要求進行授權，系統不支援其他授權通訊協定。如果您的應用程式採用使用 Google 帳戶登入功能，系統會為您處理部分授權事項。
使用 OAuth 2.0 對要求進行授權
所有 AdMob API 要求都必須獲得已驗證使用者的授權。
您必須使用 OAuth 用戶端 ID 進行這項程序。
取得 OAuth 用戶端 ID
或者，您也可以在「憑證」頁面中建立一個。
OAuth 2.0 授權程序 (或「流程」) 的細節會根據您編寫的應用程式類型而有所不同。下列一般程序適用於所有應用程式類型：
- 當應用程式需要存取使用者資料時，會向 Google 要求特定的存取範圍。
- Google 會向使用者顯示同意畫面，請對方授權您的應用程式要求部分資料。
- 如果使用者同意，Google 即會授予短期存取權杖給您的應用程式。
- 您的應用程式向使用者要求資料，並且在要求中附上存取權杖。
- 如果 Google 判定您的要求與權杖有效，便會傳回您要求的資料。
部分流程包含額外步驟，例如使用「更新權杖」來取得新的存取權杖。如要進一步瞭解各類應用程式的流程，請參閱 Google 的 OAuth 2.0 說明文件。
以下列出 AdMob API 的 OAuth 2.0 範圍相關資訊：
| 範圍 |
意義 |
https://www.googleapis.com/auth/admob.readonly |
查看所有 AdMob 資料。這些 AdMob 資料可能包含帳戶資訊、廣告空間和中介服務設定、報表以及其他資料。但不含付款或廣告活動詳細資料等機密資料。
|
https://www.googleapis.com/auth/admob.report |
查看廣告成效和收益報表。查看發布商 ID、時區和預設貨幣代碼。 |
如要透過 OAuth 2.0 要求存取權，您的應用程式需要範圍資訊，以及 Google 在您註冊應用程式時提供的資訊 (例如用戶端 ID 和用戶端密碼)。
提示：Google API 用戶端程式庫可以為您處理部分授權程序，且適用於多種程式設計語言；詳情請參閱程式庫和範例頁面。
除非另有註明，否則本頁面中的內容是採用創用 CC 姓名標示 4.0 授權，程式碼範例則為阿帕契 2.0 授權。詳情請參閱《Google Developers 網站政策》。Java 是 Oracle 和/或其關聯企業的註冊商標。
上次更新時間：2025-08-31 (世界標準時間)。
[null,null,["上次更新時間：2025-08-31 (世界標準時間)。"],[[["\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,["# Authorization\n\nEvery request your application sends to the AdMob API must include an authorization token. The token also identifies your application to Google.\n\n#### About 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\n#### Authorizing 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."]]
