AI-generated Key Takeaways
-
Display & Video 360 API v2 is sunset and this document outlines the creation of new custom bidding scripts using the API.
-
The API request utilizes an HTTP POST method to a specific endpoint with path and query parameters defining the script ownership and parent algorithm.
-
Both request and response bodies involve a
CustomBiddingScript
object for data exchange regarding the script details. -
Proper authorization using the
https://www.googleapis.com/auth/display-video
scope is required for successful API interaction.
- HTTP request
- Path parameters
- Query parameters
- Request body
- Response body
- Authorization scopes
- Try it!
Creates a new custom bidding script. Returns the newly created script if successful.
HTTP request
POST https://displayvideo.googleapis.com/v2/customBiddingAlgorithms/{customBiddingAlgorithmId}/scripts
The URL uses gRPC Transcoding syntax.
Path parameters
Parameters | |
---|---|
customBiddingAlgorithmId |
Required. The ID of the custom bidding algorithm that owns the script. |
Query parameters
Parameters | |
---|---|
Union parameter owner . Required. Identifies the DV360 entity that owns the parent custom bidding algorithm. 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 custom bidding algorithm. Only this partner will have write access to this custom bidding script. |
advertiserId |
The ID of the advertiser that owns the parent custom bidding algorithm. |
Request body
The request body contains an instance of CustomBiddingScript
.
Response body
If successful, the response body contains a newly created instance of CustomBiddingScript
.
Authorization scopes
Requires the following OAuth scope:
https://www.googleapis.com/auth/display-video
For more information, see the OAuth 2.0 Overview.