AI-generated Key Takeaways
- 
          Display & Video 360 API v3 has sunset and users should use v4 instead. 
- 
          This page describes how to get a custom bidding algorithm using the v3 API. 
- 
          The request requires a custom bidding algorithm ID as a path parameter and either a partner ID or advertiser ID as a query parameter. 
- 
          The request body must be empty and the response body will contain a CustomBiddingAlgorithm instance if successful. 
- 
          The request requires the https://www.googleapis.com/auth/display-videoOAuth scope for authorization.
- HTTP request
- Path parameters
- Query parameters
- Request body
- Response body
- Authorization scopes
- Try it!
Gets a custom bidding algorithm.
HTTP request
GET https://displayvideo.googleapis.com/v3/customBiddingAlgorithms/{customBiddingAlgorithmId}
The URL uses gRPC Transcoding syntax.
Path parameters
| Parameters | |
|---|---|
| customBiddingAlgorithmId | 
 Required. The ID of the custom bidding algorithm to fetch. | 
Query parameters
| Parameters | |
|---|---|
| Union parameter accessor. Required. Identifies which DV360 entity the request is being made within. The Get request will only return a custom bidding algortihm entity that is accessible to the DV360 entity identified within theaccessor.accessorcan be only one of the following: | |
| partnerId | 
 The ID of the DV360 partner that has access to the custom bidding algorithm. | 
| advertiserId | 
 The ID of the DV360 partner that has access to the custom bidding algorithm. | 
Request body
The request body must be empty.
Response body
If successful, the response body contains an instance of CustomBiddingAlgorithm.
Authorization scopes
Requires the following OAuth scope:
- https://www.googleapis.com/auth/display-video
For more information, see the OAuth 2.0 Overview.