Sign in

v1

latestOpenAPI 3.1.02026-07-24251250397.8 KB
SSAI

Explicit SSAI Session Initialization Endpoint

Initializes the SSAI session and returns a JSON with the URLs needed to stream content and track the session

If URL-signing is enabled, follow the instructions for creating a properly formed request.

For DRM-protected content, use the Single media, playback metadata endpoint and include the ad_config_id query parameter to request the SSAI version with DRM support.

post/v2/sites/{site_id}/media/{media_id}/ssai.{manifest_extension}

Path parameters

site_idstring required

Property or site ID that owns a piece of media

media_idstring required

Eight-character, alphanumeric ID that uniquely identifies the media

This can be found on the video detail page in the dashboard.

manifest_extension'm3u8' | 'mpd' required

The file extension of the manifest

Possible values:

  • m3u8: HLS manifest
  • mpd: DASH manifest

Query parameters

ad_config_idstring required

Unique identifier of the ad config

schema'' | 'aws'

(Optional) Schema format for the requested SSAI media manifest

The schema query parameter is either omitted/empty or aws. When empty, successful JSON uses manifest_url and session_info. When schema=aws, the same values are returned as manifestUrl and trackingUrl.

Request body

reporting_modestring

Indicates whether tracking beacons are sent by the client or the server To request an AWS schema, this value must be passed as 'reportingMode' (in camelCase). This value is passed through to the 'session_info' or 'trackingUrl' URL as a query parameter.

Possible values:

  • 'client': (Default) The player or client sends tracking beacons
  • 'server': The server sends tracking beacons

Response

SSAI session started successfully. JSON containing the manifest URL and session info URL.

May include an optional warning when playback URLs are still returned but something did not match the ideal path.

OR