AI-generated Key Takeaways
-
Display & Video 360 API v3 has sunset, and users should use v4 instead.
-
This method replaces all sites under a single channel using the provided sites in the request.
-
This method regularly experiences high latency, and increasing the default timeout is recommended.
-
The request requires specifying the channel ID and either an advertiser ID or partner ID as the owner.
-
The request body includes a list of new sites to replace the existing ones.
Replaces all of the sites under a single channel.
The operation will replace the sites under a channel with the sites provided in ReplaceSitesRequest.new_sites
.
This method regularly experiences high latency. We recommend increasing your default timeout to avoid errors.
HTTP request
POST https://displayvideo.googleapis.com/v3/advertisers/{advertiserId}/channels/{channelId}/sites:replace
The URL uses gRPC Transcoding syntax.
Path parameters
Parameters | |
---|---|
channelId |
Required. The ID of the parent channel whose sites will be replaced. |
Union parameter owner . Required. Identifies the DV360 entity that owns the parent channel. It can be either a partner or an advertiser. owner can be only one of the following: |
|
advertiserId |
The ID of the advertiser that owns the parent channel. |
Request body
The request body contains data with the following structure:
JSON representation |
---|
{ "newSites": [ { object ( |
Fields | |
---|---|
newSites[] |
The sites that will replace the existing sites assigned to the channel, specified as a list of |
Union field owner . Required. Identifies the DV360 entity that owns the parent channel. It can be either a partner or an advertiser. owner can be only one of the following: |
|
partnerId |
The ID of the partner that owns the parent channel. |
advertiserId |
The ID of the advertiser that owns the parent channel. |
Response body
If successful, the response body contains an instance of ReplaceSitesResponse
.
Authorization scopes
Requires the following OAuth scope:
https://www.googleapis.com/auth/display-video
For more information, see the OAuth 2.0 Overview.