AI-generated Key Takeaways
- 
          Display & Video 360 API v3 has sunset and users should use v4 instead. 
- 
          The API allows creating an assignment between a location and a location list using a POST request. 
- 
          The request requires advertiser ID and location list ID as path parameters. 
- 
          The request body should contain an instance of AssignedLocation and the response body will contain a newly created instance if successful. 
- 
          The API call requires the https://www.googleapis.com/auth/display-videoauthorization scope.
Creates an assignment between a location and a location list.
HTTP request
POST https://displayvideo.googleapis.com/v3/advertisers/{advertiserId}/locationLists/{locationListId}/assignedLocations
The URL uses gRPC Transcoding syntax.
Path parameters
| Parameters | |
|---|---|
| advertiserId | 
 Required. The ID of the DV360 advertiser to which the location list belongs. | 
| locationListId | 
 Required. The ID of the location list for which the assignment will be created. | 
Request body
The request body contains an instance of AssignedLocation.
Response body
If successful, the response body contains a newly created instance of AssignedLocation.
Authorization scopes
Requires the following OAuth scope:
- https://www.googleapis.com/auth/display-video
For more information, see the OAuth 2.0 Overview.