Setting up Auth
Stay organized with collections
Save and categorize content based on your preferences.
DV360 seller api onboarding
There are a few major steps to onboard an API for DV360 Seller API. DV360 Seller API is exposed as allowlist based Google Cloud API, and uses OAuth for Authentication.
Allowlist process will be handled by contacting the DV360 Seller API team.
Onboarding steps:
- Sign up a Google Account by going to https://console.cloud.google.com/
- This account will be used to manage access tokens for your production client. Don't use your personal gmail account.
- The account can't be a Google Group.
- If you are using an existing Google Cloud project: The account must be an administrator of the project.
- Contact Google DV360 with the account information you have sign up to have it added to allow list.
- Wait for your account to be added to allow list.
- Optional and non-blocking: Submit an OAuth verification
review request for your app in order to access the scope(doubleclickbidmanager).
- Go to https://console.cloud.google.com/. Navigate to API & Services -> Library -> Private. You should be able to see DV360 Seller API listed as one of the API available to you.
- Enable DV360 Seller API
- Navigate to Credentials -> Create a Credential -> Service Account Key. Follow instructions here: https://developers.google.com/identity/protocols/OAuth2ServiceAccount
Set up a service account:
Note: Let us known if you would like to re-use an existing service account, such as for the DV360 Reporting API.
Google Cloud API authentication and authorization (commonly grouped together as "auth") is typically done using a service account. A service account allows your code to send application credentials directly to the Cloud API. A service account, like a user account, is represented by an email address. Unlike a user account, however, a service account belongs only to an application, and may only be used to access the API for which it was created. As an example, we will show how to create service account credentials using the Google Cloud Platform Console.
Using the Google Cloud Console
From the Google Cloud Console API Manager→Credentials page, select "Create credentials→Service account key".
Next, select "New service account" from the "Service account" drop-down.
Type a "Name" for this service account. This name will be used as the default name for your "Service account ID" (to the left of the "@" in the generated service account ID address), but you can change this service account ID name if you wish. These names can be arbitrary; it is only important that you remember them. Under "Key type," we recommend that you leave this value as "JSON". Click "Create", and the GCP Console will generate a JSON key (as a .json text file), prompt you to download the file to your computer, and display a Service account created dialog box.
The generated JSON key will be similar to the following sample JSON key:
{
"type": "service_account",
"project_id": "project-id",
"private_key_id": "some_number",
"private_key": "-----BEGIN PRIVATE KEY-----\n....
=\n-----END PRIVATE KEY-----\n",
"client_email": "<api-name>api@project-id.iam.gserviceaccount.com",
"client_id": "...",
"auth_uri": "https://accounts.google.com/o/oauth2/auth",
"token_uri": "https://accounts.google.com/o/oauth2/token",
"auth_provider_x509_cert_url": "https://www.googleapis.com/oauth2/v1/certs",
"client_x509_cert_url": "https://www.googleapis.com/...<api-name>api%40project-id.iam.gserviceaccount.com"
}
Store this JSON file securely, as it contains your private key (and this file is the only copy of that key). You will need to refer to this service account key file within your code when you wish to send credentials to the Google Cloud Platform API.
- Contact DV360 with the service account information you created. Specifically we will need the email for this service account. This is another allowlist process for Authorization.
- Once your service account is authorized to call API, you can refer to https://developers.google.com/display-video/seller for API documentation. To get auth token manually, see instructions here: https://github.com/google/oauth2l. (You will need to have already downloaded the JSON version of your service account key). There are also detailed instructions on how to programatically get Oauth Token here: https://cloud.google.com/docs/authentication/production.
Important: The OAuth scope need to be 'doubleclickbidmanager'
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-04-16 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-04-16 UTC."],[[["\u003cp\u003eDV360 Seller API onboarding requires allowlisting by the DV360 team for both your Google Account and a dedicated service account.\u003c/p\u003e\n"],["\u003cp\u003eYou must create a non-personal Google Account and a service account key for API access.\u003c/p\u003e\n"],["\u003cp\u003eYour application needs to undergo OAuth verification and use the 'doubleclickbidmanager' scope.\u003c/p\u003e\n"],["\u003cp\u003eDetailed API documentation and authentication instructions are available at the provided links after allowlisting.\u003c/p\u003e\n"],["\u003cp\u003eContact the DV360 Seller API team to initiate the allowlisting process and for any assistance.\u003c/p\u003e\n"]]],["To onboard the DV360 Seller API, first sign up for a Google Cloud account. Next, contact the DV360 team to be added to the allowlist. After allowlisting, submit an OAuth verification request. In the Google Cloud Console, enable the DV360 Seller API, then create a service account key, downloading the JSON file. Contact DV360 again to authorize this service account. Finally, obtain an OAuth token and ensure the scope is 'doubleclickbidmanager'.\n"],null,["# Setting up Auth\n\nDV360 seller api onboarding\n\n\nThere are a few major steps to onboard an API for DV360 Seller API. DV360 Seller API is exposed as allowlist based Google Cloud API, and uses OAuth for Authentication.\n\n\nAllowlist process will be handled by contacting the DV360 Seller API team.\n| **Note:** If your app accesses the DV360 Seller 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\n\nOnboarding steps:\n\n1. Sign up a Google Account by going to \u003chttps://console.cloud.google.com/\u003e\n - This account will be used to manage access tokens for your production client. Don't use your personal gmail account.\n - The account can't be a Google Group.\n - **If you are using an existing Google Cloud project:** The account must be an administrator of the project.\n2. Contact Google DV360 with the account information you have sign up to have it added to allow list.\n3. Wait for your account to be added to allow list.\n4. **Optional and non-blocking:** Submit an [OAuth verification\n review](//support.google.com/cloud/answer/7454865#verification) request for your app in order to access the scope(doubleclickbidmanager).\n5. Go to \u003chttps://console.cloud.google.com/\u003e. Navigate to API \\& Services -\\\u003e Library -\\\u003e Private. You should be able to see DV360 Seller API listed as one of the API available to you.\n6. Enable DV360 Seller API\n7. Navigate to Credentials -\\\u003e Create a Credential -\\\u003e Service Account Key. Follow instructions here: \u003chttps://developers.google.com/identity/protocols/OAuth2ServiceAccount\u003e\n\n\n Set up a service account:\n **Note:** Let us known if you would like to re-use an existing service account, such as for the [DV360 Reporting API](https://developers.google.com/display-video/exchange-reporting/guides/getting-started/setting-up-auth).\n\n\n Google Cloud API authentication and authorization (commonly grouped together as \"auth\") is typically done using a service account. A service account allows your code to send application credentials directly to the Cloud API. A service account, like a user account, is represented by an email address. Unlike a user account, however, a service account belongs only to an application, and may only be used to access the API for which it was created. As an example, we will show how to create service account credentials using the Google Cloud Platform Console.\n\n ### Using the Google Cloud Console\n\n\n From the Google Cloud Console [API Manager→Credentials](https://console.cloud.google.com/apis/credentials) page, select \"Create credentials→Service account key\".\n\n\n Next, select \"New service account\" from the \"Service account\" drop-down.\n\n\n Type a \"Name\" for this service account. This name will be used as the default name for your \"Service account ID\" (to the left of the \"@\" in the generated service account ID address), but you can change this service account ID name if you wish. These names can be arbitrary; it is only important that you remember them. Under \"Key type,\" we recommend that you leave this value as \"JSON\". Click \"Create\", and the GCP Console will generate a JSON key (as a `.json` text file), prompt you to download the file to your computer, and display a **Service account created** dialog box.\n\n\n The generated JSON key will be similar to the following sample JSON key: \n\n ```carbon\n {\n \"type\": \"service_account\",\n \"project_id\": \"project-id\",\n \"private_key_id\": \"some_number\",\n \"private_key\": \"-----BEGIN PRIVATE KEY-----\\n....\n =\\n-----END PRIVATE KEY-----\\n\",\n \"client_email\": \"\u003capi-name\u003eapi@project-id.iam.gserviceaccount.com\",\n \"client_id\": \"...\",\n \"auth_uri\": \"https://accounts.google.com/o/oauth2/auth\",\n \"token_uri\": \"https://accounts.google.com/o/oauth2/token\",\n \"auth_provider_x509_cert_url\": \"https://www.googleapis.com/oauth2/v1/certs\",\n \"client_x509_cert_url\": \"https://www.googleapis.com/...\u003capi-name\u003eapi%40project-id.iam.gserviceaccount.com\"\n }\n ```\n\n\n Store this JSON file securely, as it contains your private key (and this file is the only copy of that key). You will need to refer to this service account key file within your code when you wish to send credentials to the Google Cloud Platform API.\n8. Contact DV360 with the**service account**information you created. Specifically we will need the email for this service account. This is another allowlist process for Authorization.\n9. Once your service account is authorized to call API, you can refer to https://developers.google.com/display-video/seller for API documentation. To get auth token manually, see instructions here: \u003chttps://github.com/google/oauth2l\u003e. (You will need to have already downloaded the JSON version of your service account key). There are also detailed instructions on how to programatically get Oauth Token here: \u003chttps://cloud.google.com/docs/authentication/production\u003e.\n\n\n**Important: The OAuth scope need to be 'doubleclickbidmanager'**"]]
