AI-generated Key Takeaways
- 
          
This document details how to list queries created by the current user using an HTTP GET request to
https://doubleclickbidmanager.googleapis.com/v2/queries. - 
          
The request supports query parameters such as
pageSize,pageToken, andorderByto control the pagination and sorting of results. - 
          
The request body must be empty, and the response body contains a list of queries and an optional
nextPageTokenfor pagination. - 
          
Accessing this method requires the
https://www.googleapis.com/auth/doubleclickbidmanagerOAuth scope. 
Lists queries created by the current user.
HTTP request
GET https://doubleclickbidmanager.googleapis.com/v2/queries
The URL uses gRPC Transcoding syntax.
Query parameters
| Parameters | |
|---|---|
pageSize | 
                
                   
 Maximum number of results per page. Must be between   | 
              
pageToken | 
                
                   
 A token identifying which page of results the server should return. Typically, this is the value of   | 
              
orderBy | 
                
                   
 Field to sort the list by. Accepts the following values: 
 The default sorting order is ascending. To specify descending order for a field, add the suffix   | 
              
Request body
The request body must be empty.
Response body
If successful, the response body contains data with the following structure:
| JSON representation | 
|---|
{
  "queries": [
    {
      object ( | 
                  
| Fields | |
|---|---|
queries[] | 
                    
                       
 The list of queries. This field 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/doubleclickbidmanager
For more information, see the OAuth 2.0 Overview.