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 script using a GET HTTP request. 
- 
          The request requires path parameters for the custom bidding algorithm and script IDs, and a query parameter to identify the owning entity (partner or advertiser). 
- 
          The request body must be empty, and a successful response will contain a CustomBiddingScript instance. 
- 
          The request requires the https://www.googleapis.com/auth/display-videoauthorization scope.
- HTTP request
- Path parameters
- Query parameters
- Request body
- Response body
- Authorization scopes
- Try it!
Gets a custom bidding script.
HTTP request
GET https://displayvideo.googleapis.com/v3/customBiddingAlgorithms/{customBiddingAlgorithmId}/scripts/{customBiddingScriptId}
The URL uses gRPC Transcoding syntax.
Path parameters
| Parameters | |
|---|---|
| customBiddingAlgorithmId | 
 Required. The ID of the custom bidding algorithm owns the script. | 
| customBiddingScriptId | 
 Required. The ID of the custom bidding script to fetch. | 
Query parameters
| Parameters | |
|---|---|
| Union parameter accessor. Required. Identifies the DV360 entity that owns the parent custom bidding algorithm. It can be either a partner or an advertiser.accessorcan 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 must be empty.
Response body
If successful, the response body contains an 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.