AI-generated Key Takeaways
- 
          Display & Video 360 API v1 has been sunset. 
- 
          This documentation outlines how to create an assignment between an inventory source and an inventory source group using a POST request. 
- 
          The request requires specifying the inventory source group ID in the path parameters and identifying the owner (partner or advertiser) in the query parameters. 
- 
          The request body should contain an instance of AssignedInventorySource, and a successful response will return a newly created instance. 
- 
          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!
Creates an assignment between an inventory source and an inventory source group.
HTTP request
POST https://displayvideo.googleapis.com/v1/inventorySourceGroups/{inventorySourceGroupId}/assignedInventorySources
The URL uses gRPC Transcoding syntax.
Path parameters
| Parameters | |
|---|---|
| inventorySourceGroupId | 
 Required. The ID of the inventory source group to which the assignment will be assigned. | 
Query parameters
| Parameters | |
|---|---|
| Union parameter owner. Required. Identifies the DV360 entity that owns the parent inventory source group. It can be either a partner or an advertiser.ownercan be only one of the following: | |
| partnerId | 
 The ID of the partner that owns the parent inventory source group. Only this partner will have write access to this assigned inventory source. | 
| advertiserId | 
 The ID of the advertiser that owns the parent inventory source group. The parent partner will not have access to this assigned inventory source. | 
Request body
The request body contains an instance of AssignedInventorySource.
Response body
If successful, the response body contains a newly created instance of AssignedInventorySource.
Authorization Scopes
Requires the following OAuth scope:
- https://www.googleapis.com/auth/display-video
For more information, see the OAuth 2.0 Overview.