Requested page size. Must be between 1 and 200. If unspecified will default to 100. Returns error code INVALID_ARGUMENT if an invalid value is specified.
pageToken
string
A token identifying a page of results the server should return. Typically, this is the value of nextPageToken returned from the previous call to customBiddingAlgorithms.list method. If not specified, the first page of results will be returned.
orderBy
string
Field by which to sort the list. Acceptable values are:
displayName (default)
The default sorting order is ascending. To specify descending order for a field, a suffix "desc" should be added to the field name. Example: displayName desc.
filter
string
Allows filtering by custom bidding algorithm fields.
Supported syntax:
Filter expressions are made up of one or more restrictions.
Restrictions can be combined by AND. A sequence of restrictions implicitly uses AND.
A restriction has the form of {field} {operator} {value}.
The customBiddingAlgorithmType field must use the EQUALS (=) operator.
The displayName field must use the HAS (:) operator.
Supported fields:
customBiddingAlgorithmType
displayName
Examples:
All custom bidding algorithms for which the display name contains "politics": displayName:"politics".
All custom bidding algorithms for which the type is "SCRIPT_BASED": customBiddingAlgorithmType=SCRIPT_BASED
The length of this field should be no more than 500 characters.
Union parameter accessor. Required. Identifies which DV360 entity the request is being made within. The LIST request will only return custom bidding algortihm entities that are accessible to the DV360 entity identified within the accessor. To perform LIST request, user needs to have permission to the accessor entity. accessor can be only one of the following:
A token to retrieve the next page of results. Pass this value in the pageToken field in the subsequent call to ListCustomBiddingAlgorithmsRequest method to retrieve the next page of results. If this field is null, it means this is the last page.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2024-09-18 UTC."],[[["Lists custom bidding algorithms accessible to the current user for bidding strategies, ordered by the `orderBy` parameter."],["Filter results by algorithm type and display name using the `filter` parameter, with a maximum length of 500 characters."],["Specify `pageSize` (1-200, default 100) and use `pageToken` for pagination through results."],["Requires authorization with the `https://www.googleapis.com/auth/display-video` scope."],["Display & Video 360 API v1 has been sunset."]]],["This document outlines the process for listing custom bidding algorithms via the Display & Video 360 API. Key actions involve sending a `GET` request to `https://displayvideo.googleapis.com/v1/customBiddingAlgorithms`. Users can specify `pageSize`, `pageToken`, `orderBy`, and `filter` in the query parameters. The `accessor` parameter is required and it identifies which entity is the request being made within. The response returns a list of custom bidding algorithms and a `nextPageToken` for pagination, if applicable, adhering to specific authorization scopes.\n"]]