AI-generated Key Takeaways
- 
          This document details the advertisers.negativeKeywordLists.listmethod for Display & Video 360 API v3, which has been sunset and replaced by v4.
- 
          The method lists negative keyword lists associated with a specific advertiser ID, which is a required path parameter. 
- 
          Optional query parameters include pageSizeto specify the number of results per page andpageTokenfor paginating through results.
- 
          The request body for this method must be empty, and the response body contains a list of negative keyword lists and a token for the next page of results. 
- 
          Authorization requires the https://www.googleapis.com/auth/display-videoOAuth scope.
- HTTP request
- Path parameters
- Query parameters
- Request body
- Response body
- Authorization scopes
- Try it!
Lists negative keyword lists based on a given advertiser id.
HTTP request
GET https://displayvideo.googleapis.com/v3/advertisers/{advertiserId}/negativeKeywordLists
The URL uses gRPC Transcoding syntax.
Path parameters
| Parameters | |
|---|---|
| advertiserId | 
 Required. The ID of the DV360 advertiser to which the fetched negative keyword lists belong. | 
Query parameters
| Parameters | |
|---|---|
| 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  | 
Request body
The request body must be empty.
Response body
Response message for NegativeKeywordListService.ListNegativeKeywordLists.
If successful, the response body contains data with the following structure:
| JSON representation | 
|---|
| {
  "negativeKeywordLists": [
    {
      object ( | 
| Fields | |
|---|---|
| negativeKeywordLists[] | 
 The list of negative keyword lists. 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.