AI-generated Key Takeaways
- 
          Display & Video 360 API v3 has sunset and users should use v4 instead. 
- 
          This page details how to update an existing custom bidding algorithm using the v3 API via a PATCH request. 
- 
          Updating a custom bidding algorithm assigned to a line item will return an error. 
- 
          The request requires specifying the unique ID of the custom bidding algorithm and an update mask. 
- HTTP request
- Path parameters
- Query parameters
- Request body
- Response body
- Authorization scopes
- Try it!
Updates an existing custom bidding algorithm. Returns the updated custom bidding algorithm if successful.
Requests updating a custom bidding algorithm assigned to a line item will return an error.
HTTP request
PATCH https://displayvideo.googleapis.com/v3/customBiddingAlgorithms/{customBiddingAlgorithm.customBiddingAlgorithmId}
The URL uses gRPC Transcoding syntax.
Path parameters
| Parameters | |
|---|---|
| customBiddingAlgorithm.customBiddingAlgorithmId | 
 Output only. The unique ID of the custom bidding algorithm. Assigned by the system. | 
Query parameters
| Parameters | |
|---|---|
| updateMask | 
 Required. The mask to control which fields to update. This is a comma-separated list of fully qualified names of fields. Example:  | 
Request body
The request body contains an instance of CustomBiddingAlgorithm.
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.