AI-generated Key Takeaways
-
Display & Video 360 API v3 has sunset and users should transition to v4.
-
This page provides documentation for getting a custom list using the v3 API.
-
The request requires specifying the custom list ID as a path parameter and either an advertiser ID as a query parameter to identify the accessible entity.
-
A successful request returns a CustomList instance in the response body and requires the
https://www.googleapis.com/auth/display-videoOAuth scope.
- HTTP request
- Path parameters
- Query parameters
- Request body
- Response body
- Authorization scopes
- Try it!
Gets a custom list.
HTTP request
GET https://displayvideo.googleapis.com/v3/customLists/{customListId}
The URL uses gRPC Transcoding syntax.
Path parameters
| Parameters | |
|---|---|
customListId |
Required. The ID of the custom list to fetch. |
Query parameters
| Parameters | |
|---|---|
Union parameter accessor. Required. Identifies which DV360 entity the request is being made within. The GET request will only return custom list entities that are accessible to the DV360 entity identified within the accessor. accessor can be only one of the following: |
|
advertiserId |
The ID of the DV360 advertiser that has access to the fetched custom lists. |
Request body
The request body must be empty.
Response body
If successful, the response body contains an instance of CustomList.
Authorization scopes
Requires the following OAuth scope:
https://www.googleapis.com/auth/display-video
For more information, see the OAuth 2.0 Overview.