The DV360 Exchange Reporting API provides Third-Party Exchange (3PE) partners
with programmatic access to performance reports from Display \& Video 360.

> [!NOTE]
> **Note:** This API is exclusively for Third-Party Exchange (3PE) partners. Google does not support onboarding for standard Display \& Video 360 users.

The DV360 Exchange Reporting API is exposed as an allowlist based Google Cloud
API which uses OAuth. The allowlist process is handled by the DV360 Exchange
Reporting API team.

> [!IMPORTANT]
> **Key Point:** Before your app can access the DV360 Exchange Reporting API, it must first pass the [OAuth verification
> review](https://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](https://support.google.com/cloud/answer/7454865) or get answers to [frequently
> asked questions about app
> verification](https://support.google.com/cloud/answer/9110914).

## Procedure

Here are the DV360 Exchange Reporting API onboarding steps:

1. Sign up a Google Account on the [Google Cloud
   console](https://console.cloud.google.com).

   Note that this account is to be used to manage access tokens for your
   production client, so don't use your personal Gmail account.
2. Contact Google DV360 with the account information to have it added to the
   allowlist.

3. After you've been notified that you're on the allowlist, request an [OAuth
   verification review](https://support.google.com/cloud/answer/7454865#verification)
   to get your app access to the `doubleclickbidmanager` scope.

4. Sign in on the [Google Cloud console](https://console.cloud.google.com).

   Navigate to **API \& Services \> Library \> Private**. You should see a DV360
   Exchange Reporting API listed as one of the API available to you. Enable the
   DV360 Exchange Reporting API.
5. Navigate to **Credentials \> Create a Credential \> Service Account Key** .
   Follow the [instructions to create a service
   account](https://developers.google.com/identity/protocols/OAuth2ServiceAccount).

## Service account

A service account allows your code to send application credentials directly to
the 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 can only be used to access the API for which it was created.

Here are the steps to create service account credentials using the Google Cloud
console:

1. From the [API Manager \>
   Credentials](https://console.cloud.google.com/apis/credentials) page, select
   **Create credentials→Service account key**.

   ![](https://developers.google.com/static/display-video/exchange-reporting/guides/getting-started/images/image1.png)
2. Select **New service account** from the **Service account** drop-down.

   ![](https://developers.google.com/static/display-video/exchange-reporting/guides/getting-started/images/image2.png)

   Enter a **Name** for this service account. This name is used as the default
   name for your **Service account ID** , to the left of the `@` in the
   generated service account ID address.

   Under **Key type** , we recommend that you leave this value as `JSON`. Click
   **Create** to generate a JSON key as a `.json` text file. When prompted,
   download the file to your computer and a **Service account created** dialog
   is displayed.

   ![](https://developers.google.com/static/display-video/exchange-reporting/guides/getting-started/images/image3.png)

   Here is a 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"
       }

3. Store your JSON file securely, as it contains your private key, and this
   file is the only copy of that key. The credentials in this file are needed
   when your code make calls to the API.

4. Contact DV360 with the *service account* information you created,
   specifically, the email address of the service account. This is part of the
   allowlist process for API access.

## Access token

After your service account is authorized to make calls to the API, you can
proceed with the examples in the API guides. To get an access token manually,
you can use a tool such as [oauth2l](https://github.com/google/oauth2l); or, use one
of our [client
libraries](https://cloud.google.com/docs/authentication/client-libraries) to
authenticate programmatically.

> [!IMPORTANT]
> **Important:** In your API calls, the OAuth scope needs to be `doubleclickbidmanager`.