向请求授权
使用集合让一切井井有条
根据您的偏好保存内容并对其进行分类。
当您的应用请求私有数据时，该请求必须获得经过身份验证的
有权访问相应数据的用户。
<ph type="x-smartling-placeholder">
您的应用向 Bid Manager API 发送的每个请求都必须包含授权令牌。令牌
也能让 Google 识别您的应用。
关于授权协议
您的应用必须使用 OAuth 2.0 授权请求。
其他任何授权协议均不受支持。如果您的应用使用 Google 登录功能，则系统会针对
。
使用 OAuth 2.0 向请求授权
向 Bid Manager API 发出的所有请求都必须由已通过身份验证的用户授权。
详细的授权流程可能会因为 OAuth 2.0 的不同而
了解您所编写的应用类型以下常规流程适用于所有应用类型：
- 创建应用时，您需要使用 Google API 控制台进行注册。然后，Google 会向您提供
例如客户端 ID 和客户端密钥。
- 提交 OAuth 验证
审核请求，以便访问 Bid Manager API 范围。
- 在 Google API 控制台中激活 Bid Manager API。（如果 API 未在
API 控制台，然后跳过此步骤。）
- 当您的应用需要访问用户数据时，它会请求 Google 提供特定范围
访问权限。
- Google 会向用户显示同意界面，让用户授权您的应用使用
访问其部分数据
- 如果用户批准，Google 会为您的应用提供一个短期访问令牌。
- 您的应用请求用户数据，并在请求中附上该访问令牌。
- 如果 Google 确定您的请求和令牌有效，就会返回您请求的数据。
有些流程还包含其他步骤，例如使用刷新令牌获取新访问权限
词元。如需详细了解适用于各类应用的流程，请参阅 Google 的 OAuth 2.0 文档。
OAuth 范围
以下是 Bid Manager API 的 OAuth 2.0 范围信息：
| 范围 |
含义 |
https://www.googleapis.com/auth/doubleclickbidmanager |
读取/写入权限。 |
要通过 OAuth 2.0 请求访问权限，您的应用需要范围信息以及
Google 在您注册应用时提供的信息（如客户端 ID 和
客户端密钥）。
如未另行说明，那么本页面中的内容已根据知识共享署名 4.0 许可获得了许可，并且代码示例已根据 Apache 2.0 许可获得了许可。有关详情，请参阅 Google 开发者网站政策。Java 是 Oracle 和/或其关联公司的注册商标。
最后更新时间 (UTC)：2025-07-25。
[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["没有我需要的信息","missingTheInformationINeed","thumb-down"],["太复杂/步骤太多","tooComplicatedTooManySteps","thumb-down"],["内容需要更新","outOfDate","thumb-down"],["翻译问题","translationIssue","thumb-down"],["示例/代码问题","samplesCodeIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC)：2025-07-25。"],[[["\u003cp\u003eApplications need authorization from an authenticated user to access private data through the Bid Manager API.\u003c/p\u003e\n"],["\u003cp\u003eThe Bid Manager API exclusively supports OAuth 2.0 for authorization and requires apps to pass an OAuth verification review.\u003c/p\u003e\n"],["\u003cp\u003eApps must be registered using the Google API Console, undergo an OAuth verification review, and request specific scopes for data access.\u003c/p\u003e\n"],["\u003cp\u003eUpon user consent, Google provides a short-lived access token which the app uses to make authorized requests for user data.\u003c/p\u003e\n"]]],["Apps requesting private data through the Bid Manager API must be authorized by an authenticated user via OAuth 2.0. The process involves registering the app with Google, submitting an OAuth verification request, and activating the API. The app then requests a specific access scope, prompting a user consent screen. Upon approval, Google issues a short-lived access token. This token is included in data requests, allowing Google to validate the request and return data. The available scope is for read/write access.\n"],null,["# Authorize Requests\n\nWhen your app requests private data, the request must be authorized by an authenticated\nuser who has access to that data.\n| **Note:** If your app accesses the Bid Manager API, it must pass the [OAuth verification review](//support.google.com/cloud/answer/7454865#verification). If you see **unverified app** on the screen when testing your app, you must submit a verification request to remove it. Learn more about [unverified apps](//support.google.com/cloud/answer/7454865) or get answers to [frequently asked questions about app\n| verification](//support.google.com/cloud/answer/9110914).\n\nEvery request your app sends to the Bid Manager API must include an authorization token. The token\nalso identifies your app to Google.\n\nAbout authorization protocols\n-----------------------------\n\nYour app must use [OAuth 2.0](/identity/protocols/OAuth2) to authorize requests.\nNo other authorization protocols are supported. If your app uses [Google Sign-In](/identity#google-sign-in), some aspects of authorization are handled for\nyou.\n\nAuthorizing requests with OAuth 2.0\n-----------------------------------\n\nAll requests to the Bid Manager API must be authorized by an authenticated user.\n\nThe details of the authorization process, or \"flow,\" for OAuth 2.0 vary somewhat depending\non what kind of app you're writing. The following general process applies to all app types:\n\n1. When you create your app, you register it using the [Google API Console](https://console.cloud.google.com/). Google then provides information you'll need later, such as a client ID and a client secret.\n2. Submit an [OAuth verification\n review](//support.google.com/cloud/answer/7454865#verification) request for your app in order to access the Bid Manager API scope.\n3. Activate the Bid Manager API in the Google API Console. (If the API isn't listed in the API Console, then skip this step.)\n4. When your app needs access to user data, it asks Google for a particular **scope** of access.\n5. Google displays a **consent screen** to the user, asking them to authorize your app for access to some of their data.\n6. If the user approves, then Google gives your app a short-lived **access token**.\n7. Your app requests user data, attaching the access token to the request.\n8. 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\ntokens. For detailed information about flows for various types of apps, see Google's [OAuth 2.0 documentation](/identity/protocols/OAuth2).\n\nOAuth scope\n-----------\n\nHere's the OAuth 2.0 scope information for the Bid Manager API:\n\n| Scope | Meaning |\n|---------------------------------------------------------|--------------------|\n| `https://www.googleapis.com/auth/doubleclickbidmanager` | Read/write access. |\n\nTo request access using OAuth 2.0, your app needs the scope information, as well as\ninformation that Google supplies when you register your app (such as the client ID and the\nclient secret)."]]
