自
2025 年 9 月 8 日起，每個新委刊項都必須聲明是否會放送歐盟政治廣告。如果透過 Display & Video 360 API 和 SDF 上傳的檔案未提供聲明，系統就會失敗。如要進一步瞭解如何更新整合服務以進行這項聲明，請參閱
淘汰項目頁面。
對要求進行授權
透過集合功能整理內容
你可以依據偏好儲存及分類內容。
如果您的應用程式要求存取私人資料，必須由可存取該資料的已驗證使用者對此要求進行授權。
您的應用程式傳送至 Display & Video 360 API 的每項要求，都必須包含授權權杖。這個權杖也可讓 Google 識別您的應用程式。
關於授權通訊協定
您的應用程式必須使用 OAuth 2.0 對要求進行授權，系統不支援其他授權通訊協定。如果您的應用程式採用使用 Google 帳戶登入功能，系統會為您處理部分授權事項。
使用 OAuth 2.0 對要求進行授權
所有傳送至 Display & Video 360 API 的要求都必須由經過驗證的使用者進行授權。
OAuth 2.0 授權程序 (或「流程」) 的細節會根據您編寫的應用程式類型而有所不同。下列一般程序適用於所有應用程式類型：
- 建立應用程式後，請透過 Google API 控制台註冊應用程式。接著 Google 會向您提供稍後需要的資訊，例如用戶端 ID 和用戶端密碼。
- 在 Google API 控制台中啟用 Display & Video 360 API。(如果 API 控制台裡沒有列出該 API，則可略過這個步驟)。
- 當應用程式需要存取使用者資料時，會向 Google 要求特定的存取範圍。
- Google 會向使用者顯示同意畫面，請對方授權您的應用程式要求部分資料。
- 如果使用者同意，Google 即會授予短期存取權杖給您的應用程式。
- 您的應用程式向使用者要求資料，並且在要求中附上存取權杖。
- 如果 Google 判定您的要求與權杖有效，便會傳回您要求的資料。
部分流程包含額外步驟，例如使用「更新權杖」來取得新的存取權杖。如要進一步瞭解各類應用程式的流程，請參閱 Google 的 OAuth 2.0 說明文件。
以下列出 Display & Video 360 API 的 OAuth 2.0 範圍相關資訊：
| 範圍 |
意義 |
https://www.googleapis.com/auth/display-video |
讀取/寫入權限。 |
https://www.googleapis.com/auth/display-video-user-management |
users 服務的讀取/寫入權限。僅適用於服務帳戶使用者。 |
如要透過 OAuth 2.0 要求存取權，您的應用程式需要範圍資訊，以及 Google 在您註冊應用程式時提供的資訊 (例如用戶端 ID 和用戶端密碼)。
提示：Google API 用戶端程式庫可以為您處理部分授權程序，且適用於多種程式設計語言；詳情請參閱程式庫和範例頁面。
使用者權限
如要使用 Display & Video 360 API，驗證的 Google 帳戶必須是 Display & Video 360 使用者，且能存取相關合作夥伴或廣告客戶。
Display & Video 360 使用者必須具備下列任一使用者角色，才能讓相關合作夥伴或廣告主執行下列操作：
- 唯讀：使用
get 或 list 呼叫擷取資源，但不包括 user 資源。
- 標準：擷取、建立及更新資源。擷取具有相同合作夥伴或廣告主權限的
user 資源。
- 管理：擷取、建立及更新資源。針對您管理的合作夥伴或廣告主，擷取、建立及授予
user 資源存取權。
除非另有註明，否則本頁面中的內容是採用創用 CC 姓名標示 4.0 授權，程式碼範例則為阿帕契 2.0 授權。詳情請參閱《Google Developers 網站政策》。Java 是 Oracle 和/或其關聯企業的註冊商標。
上次更新時間：2025-08-31 (世界標準時間)。
[null,null,["上次更新時間：2025-08-31 (世界標準時間)。"],[[["\u003cp\u003eAll Display & Video 360 API requests must be authorized by an authenticated user using OAuth 2.0 and include an authorization token.\u003c/p\u003e\n"],["\u003cp\u003eApplications need to be registered with Google API Console and obtain necessary credentials, including client ID and client secret, to authorize requests.\u003c/p\u003e\n"],["\u003cp\u003eUsers authenticating with the Display & Video 360 API need the appropriate user role (Read only, Standard, or Admin) to access and manipulate resources based on their permissions.\u003c/p\u003e\n"],["\u003cp\u003eThe authorization process involves requesting specific scopes of access, user consent, and Google providing short-lived access tokens for data retrieval.\u003c/p\u003e\n"],["\u003cp\u003eGoogle API client libraries can simplify the authorization process and are available for various programming languages.\u003c/p\u003e\n"]]],["Applications accessing private data via the Display & Video 360 API must use OAuth 2.0 for authorization, including an authorization token with each request. The process involves registering the application with the Google API Console to receive credentials. When access is requested, the user is prompted to grant consent, upon approval, a short-lived access token is provided. The user must also have a valid Display & Video 360 user role (Read only, Standard, or Admin).\n"],null,["# Authorize Requests\n\nWhen your application requests private data, the request must be authorized by\nan authenticated user who has access to that data.\n\nEvery request your application sends to the Display \\& Video 360 API must include an authorization token. The token also identifies your application to Google.\n\nAbout authorization protocols\n-----------------------------\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-----------------------------------\n\nAll requests to the Display \\& Video 360 API must be authorized by an authenticated user.\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 you create your application, 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. Activate the Display \\& Video 360 API in the Google API Console. (If the API isn't listed in the API Console, then skip this step.)\n3. When your application needs access to user data, it asks Google for a particular **scope** of access.\n4. Google displays a **consent screen** to the user, asking them to authorize your application to request some of their data.\n5. If the user approves, then Google gives your application a short-lived **access token**.\n6. Your application requests user data, attaching the access token to the request.\n7. 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 Display \\& Video 360 API:\n\n| Scope | Meaning |\n|-----------------------------------------------------------------|----------------------------------------------------------------------------------|\n| `https://www.googleapis.com/auth/display-video` | Read/write access. |\n| `https://www.googleapis.com/auth/display-video-user-management` | Read/write access for `users` service. Only available for service account users. |\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](/display-video/api/guides/getting-started/libraries) for more details.\n\nUser permissions\n----------------\n\nIn order to use the Display \\& Video 360 API, the authenticating Google Account must be a\nDisplay \\& Video 360 user with access to relevant partners or advertisers.\n\nThe Display \\& Video 360 user must have one of the following [user\nroles](//support.google.com/displayvideo/answer/2723011) for the relevant partners or advertisers to do the\nfollowing actions:\n\n- **Read only** : Retrieve resources using `get` or `list` calls, excluding `user` resources.\n- **Standard** : Retrieve, create, and update resources. Retrieve `user` resources with permissions to the same partners or advertisers.\n- **Admin** : Retrieve, create, and update resources. Retrieve, create and grant access to `user` resources for the partners or advertisers you administrate."]]
