AI-generated Key Takeaways
- 
          This method lists advertisers accessible to the current user for a required single partner ID. 
- 
          The list order is determined by the orderByquery parameter.
- 
          The request body must be empty, and the response body contains a list of advertisers and a nextPageToken.
- 
          This method requires the https://www.googleapis.com/auth/display-videoOAuth scope for authorization.
Lists advertisers that are accessible to the current user.
The order is defined by the orderBy parameter.
A single partnerId is required. Cross-partner listing is not supported.
HTTP request
GET https://displayvideo.googleapis.com/v4/advertisers
The URL uses gRPC Transcoding syntax.
Query parameters
| Parameters | |
|---|---|
| partnerId | 
 Required. The ID of the partner that the fetched advertisers should all belong to. The system only supports listing advertisers for one partner at a time. | 
| pageSize | 
 Requested page size. Must be between  | 
| pageToken | 
 A token identifying a page of results the server should return. Typically, this is the value of  | 
| orderBy | 
 Field by which to sort the list. Acceptable values are: 
 The default sorting order is ascending. To specify descending order for a field, a suffix "desc" should be added to the field name. For example,  | 
| filter | 
 Allows filtering by advertiser fields. Supported syntax: 
 Supported fields: 
 Examples: 
 The length of this field should be no more than 500 characters. Reference our filter  | 
Request body
The request body must be empty.
Response body
If successful, the response body contains data with the following structure:
| JSON representation | 
|---|
| {
  "advertisers": [
    {
      object ( | 
| Fields | |
|---|---|
| advertisers[] | 
 The list of advertisers. This list will be absent if empty. | 
| nextPageToken | 
 A token to retrieve the next page of results. Pass this value in the  | 
Authorization scopes
Requires the following OAuth scope:
- https://www.googleapis.com/auth/display-video
For more information, see the OAuth 2.0 Overview.