Starting September 8, 2025, every new line item will need to declare whether or not they will serve Eurpoean Union (EU) political ads. Display & Video 360 API and SDF uploads that don't provide declarations will fail. See our deprecations page for more details on how to update your integration to make this declaration.
Stay organized with collections
Save and categorize content based on your preferences.
When your application requests private data, the request must be authorized by
an authenticated user who has access to that data.
Every request your application sends to the Display & Video 360 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 Display & Video 360 API must be authorized by an authenticated user.
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 you create your application, you register it using the Google API Console. Google then provides information you'll need later, such as a client ID and a
client secret.
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.)
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 Display & Video 360 API:
Read/write access for users service. Only available for service account users.
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.
User permissions
In order to use the Display & Video 360 API, the authenticating Google Account must be a
Display & Video 360 user with access to relevant partners or advertisers.
The Display & Video 360 user must have one of the following user
roles for the relevant partners or advertisers to do the
following actions:
Read only: Retrieve resources using get or list calls, excluding
user resources.
Standard: Retrieve, create, and update resources. Retrieve user
resources with permissions to the same partners or advertisers.
Admin: Retrieve, create, and update resources. Retrieve, create and grant
access to user resources for the partners or advertisers you administrate.
[[["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-28 UTC."],[[["\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."]]
