AI-generated Key Takeaways
-
The API allows listing Ad Breaks within a live stream using a GET request.
-
You can specify the associated LiveStreamEvent using either a
customParent
path parameter orparent
orcontent
query parameters. -
Optional query parameters like
pageSize
andpageToken
can be used for pagination of the results. -
The request body for this API call must be empty.
-
The API requires specific OAuth scopes for authorization.
API to list Ad Breaks within the live stream.
HTTP request
GET https://admanagervideo.googleapis.com/v1/{customParent=networks/*/customAssets/*}/adBreaks
The URL uses gRPC Transcoding syntax.
Path parameters
Parameters | |
---|---|
customParent |
Optional. This field identifies the LiveStreamEvent that this ad break should be associated to using the custom asset key. It must have the format of "networks/{network_code}/customAssets/{asset_code}" |
Query parameters
Parameters | |
---|---|
parent |
Optional. This field identifies the LiveStreamEvent that this ad break should be associated to using the live stream asset key. It must have the format of "networks/{network_code}/assets/{asset_code}" |
content |
Optional. This is an alternative way to identify the LiveStreamEvent, if it's associated with a piece of content within GAM. It must have the format of "networks/{network_code}/sources/{content_source_id}/content/{cms_content_id}" |
pageSize |
Optional. The maximum number of ad breaks to return. The service may return fewer than this value. If unspecified, at most 10 ad breaks will be returned. The maximum value is 100; values above 100 will be coerced to 100. |
pageToken |
Optional. A page token, received from a previous When paginating, all other parameters provided to |
Request body
The request body must be empty.
Response body
If successful, the response body contains an instance of ListAdBreaksResponse
.
Authorization Scopes
Requires one of the following OAuth scopes:
https://www.googleapis.com/auth/contentingestion
https://www.googleapis.com/auth/video-ads
For more information, see the OAuth 2.0 Overview.