AI-generated Key Takeaways
- 
          This operation replaces all negative keywords in a single negative keyword list. 
- 
          The replacement keywords are provided in the newNegativeKeywordsfield of the request body.
- 
          The HTTP request uses a POST method to a URL specifying the advertiser and negative keyword list IDs. 
- 
          The response body contains the full list of negative keywords now present in the negative keyword list. 
- 
          Authorization requires the https://www.googleapis.com/auth/display-videoOAuth scope.
Replaces all negative keywords in a single negative keyword list.
The operation will replace the keywords in a negative keyword list with keywords provided in ReplaceNegativeKeywordsRequest.new_negative_keywords.
HTTP request
POST https://displayvideo.googleapis.com/v4/advertisers/{advertiserId}/negativeKeywordLists/{negativeKeywordListId}/negativeKeywords:replace
The URL uses gRPC Transcoding syntax.
Path parameters
| Parameters | |
|---|---|
| advertiserId | 
 Required. The ID of the DV360 advertiser to which the parent negative keyword list belongs. | 
| negativeKeywordListId | 
 Required. The ID of the parent negative keyword list to which the negative keywords belong. | 
Request body
The request body contains data with the following structure:
| JSON representation | 
|---|
| {
  "newNegativeKeywords": [
    {
      object ( | 
| Fields | |
|---|---|
| newNegativeKeywords[] | 
 The negative keywords that will replace the existing keywords in the negative keyword list, specified as a list of  | 
Response body
Response message for NegativeKeywordService.ReplaceNegativeKeywords.
If successful, the response body contains data with the following structure:
| JSON representation | 
|---|
| {
  "negativeKeywords": [
    {
      object ( | 
| Fields | |
|---|---|
| negativeKeywords[] | 
 The full list of negative keywords now present in the negative keyword list. | 
Authorization scopes
Requires the following OAuth scope:
- https://www.googleapis.com/auth/display-video
For more information, see the OAuth 2.0 Overview.