Method: networks.sources.content.adBreaks.create

  • The API allows creation of an Ad Break within a live stream using a POST request.

  • Path parameters are used to identify the content associated with the LiveStreamEvent.

  • Query parameters are used to associate the ad break with a LiveStreamEvent using either the live stream asset key or the custom asset key, and can include an optional adBreakId.

  • The request body should contain an instance of AdBreak.

  • A successful response body will contain a newly created AdBreak instance.

  • Authorization requires either the https://www.googleapis.com/auth/contentingestion or https://www.googleapis.com/auth/video-ads OAuth scopes.

API to create an Ad Break within the live stream.

HTTP request

POST https://admanagervideo.googleapis.com/v1/{content=networks/*/sources/*/content/*}/adBreaks

The URL uses gRPC Transcoding syntax.

Path parameters

Parameters
content

string

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}"

Query parameters

Parameters
parent

string

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}"
customParent

string

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}"
adBreakId

string

This is the adBreakId that users can provide through the request.

Request body

The request body contains an instance of AdBreak.

Response body

If successful, the response body contains a newly created instance of AdBreak.

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.