AI-generated Key Takeaways
- 
          Display & Video 360 API v3 has sunset and users should use v4 instead. 
- 
          The content describes how to create a custom bidding script reference object for a script file. 
- 
          This process involves using a GET HTTP request to a specific URL with path and query parameters. 
- 
          The request body should be empty, and a successful response returns an instance of CustomBiddingScriptRef. 
- 
          This action 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!
Creates a custom bidding script reference object for a script file.
The resulting reference object provides a resource path to which the script file should be uploaded. This reference object should be included in when creating a new custom bidding script object.
HTTP request
GET https://displayvideo.googleapis.com/v3/customBiddingAlgorithms/{customBiddingAlgorithmId}:uploadScript
The URL uses gRPC Transcoding syntax.
Path parameters
| Parameters | |
|---|---|
| customBiddingAlgorithmId | 
 Required. The ID of the custom bidding algorithm 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.ownercan 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 CustomBiddingScriptRef.
Authorization scopes
Requires the following OAuth scope:
- https://www.googleapis.com/auth/display-video
For more information, see the OAuth 2.0 Overview.