AI-generated Key Takeaways
-
Display & Video 360 API v3 has sunset and users should use v4 instead.
-
Creating a new rules resource under an algorithm assigned to a line item will return an error.
-
The request uses a POST HTTP method to create a new rules resource.
-
Path parameters require the
customBiddingAlgorithmId
of the custom bidding algorithm that owns the rules resource. -
Query parameters require an
owner
, which can be either apartnerId
or anadvertiserId
. -
The request and response bodies contain an instance of CustomBiddingAlgorithmRules.
-
Authorization requires the
https://www.googleapis.com/auth/display-video
OAuth scope.
- HTTP request
- Path parameters
- Query parameters
- Request body
- Response body
- Authorization scopes
- Try it!
Creates a new rules resource. Returns the newly created rules resource if successful.
Requests creating a custom bidding rules resource under an algorithm assigned to a line item will return an error.
HTTP request
POST https://displayvideo.googleapis.com/v3/customBiddingAlgorithms/{customBiddingAlgorithmId}/rules
The URL uses gRPC Transcoding syntax.
Path parameters
Parameters | |
---|---|
customBiddingAlgorithmId |
Required. The ID of the custom bidding algorithm that owns the rules resource. |
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 rules resource. |
advertiserId |
The ID of the advertiser that owns the parent custom bidding algorithm. |
Request body
The request body contains an instance of CustomBiddingAlgorithmRules
.
Response body
If successful, the response body contains a newly created instance of CustomBiddingAlgorithmRules
.
Authorization scopes
Requires the following OAuth scope:
https://www.googleapis.com/auth/display-video
For more information, see the OAuth 2.0 Overview.