Method: inventorySourceGroups.patch

  • Display & Video 360 API v3 has sunset and users should use v4 instead.

  • This document describes how to update an inventory source group using the Display & Video 360 API v3 PATCH method.

  • The request requires specifying the inventorySourceGroup.inventorySourceGroupId as a path parameter and an updateMask and an owner (either partnerId or advertiserId) as query parameters.

  • The request and response bodies contain instances of InventorySourceGroup.

  • The API call requires the https://www.googleapis.com/auth/display-video OAuth scope for authorization.

Updates an inventory source group. Returns the updated inventory source group if successful.

HTTP request

PATCH https://displayvideo.googleapis.com/v3/inventorySourceGroups/{inventorySourceGroup.inventorySourceGroupId}

The URL uses gRPC Transcoding syntax.

Path parameters

Parameters
inventorySourceGroup.inventorySourceGroupId

string (int64 format)

Output only. The unique ID of the inventory source group. Assigned by the system.

Query parameters

Parameters
updateMask

string (FieldMask format)

Required. The mask to control which fields to update.

This is a comma-separated list of fully qualified names of fields. Example: "user.displayName,photo".
Union parameter owner. Required. Identifies the DV360 entity that owns the inventory source group. It can be either a partner or an advertiser. owner can be only one of the following:
partnerId

string (int64 format)

The ID of the partner that owns the inventory source group.

Only this partner has write access to this group.
advertiserId

string (int64 format)

The ID of the advertiser that owns the inventory source group.

The parent partner does not have access to this group.

Request body

The request body contains an instance of InventorySourceGroup.

Response body

If successful, the response body contains an instance of InventorySourceGroup.

Authorization scopes

Requires the following OAuth scope:

  • https://www.googleapis.com/auth/display-video

For more information, see the OAuth 2.0 Overview.