Submit a job for Channels creation/update

Submits a job to create a channel or to modify an existing one. The request body must be a valid SMIL XML playlist. For VOD2Live playlusts, the SMIL head section must contain at least the two options: - vod2live (set to True) - vod2live_start_time, in a valid ISO8601 format, as supported by mp4split. For Live playlists, the SMIL must ... [WRITEME] The SMIL body section must be non-empty. If {channel} does not exist already, a job is scheduled to create one. When a job is successfully scheduled, a 200 status is returned. The response will include a 'task_id' and a 'status_url' which can be queried to check the job status. If {channel} exists, an update is attempted. This function is mostly dedicated to modify "future" channels that are not active yet (their vod2live_start_time has not yet expired). In fact, the update will fail if: - a creation/update job is pending or running already. In this case, 503 is returned. The update can be re-attempted later. - the channel has started already (e.g. vod2live_start_time in the past). In this case, a 400 error is returned: the operation is prevented because modifying an active channel would break running streams. If you really want to update an active channel and break playout, you can do so by forcing the operation with the `force` query parameter. Use this with extreme caution. NOTICE: if your intent is to switch the channel to different content (and keep the existing archive) you should use a "transition". If instead you need to completely obliterate the channel, use the "DELETE" endpoint.

Set VOD2Live delay

Set a fixed offset in seconds to delay VOD2Live outputs to simulate live encoder latency, in order to more closely align VOD2Live and Live source media timelines. Delay must be a positive integer.

Set a default pipeline for the channel

Activate a Manifest Edit use case for this channel, based on the provided pipeline configuration. The request body must be a valid yaml pipeline configuration file. The use case is available at the default playout URI channel.isml/.{format}. The playout URI is returned on success for clarity.

Set a pipeline for this specific variant of the channel

Activate a Manifest Edit use case for this channel, based on the provided pipeline configuration. The request body must be a valid yaml pipeline configuration file. A channel variant will be created, which is available at the playout URI channel.isml/.{format}/?python_pipeline_config={variant}. The playout URI is returned on success for clarity.

Submit a job for Transitions creation/update

Submits a job to create a transition or to modify an existing one. The request body must be a valid SMIL XML playlist. For VOD2Live playlists, the SMIL head section must contain at least the two options: - vod2live (set to True) - vod2live_start_time, in a valid ISO8601 format, as supported by mp4split. For Live playlists, the SMIL must ... [WRITEME] The SMIL body section must be non-empty. If {transition} does not exist already, a job is scheduled to create one. When a job is successfully scheduled, a 200 status is returned. The response will include a 'task_id' and a 'status_url' which can be queried to check the job status. If {transition} exists, an update is attempted. This function is mostly dedicated to modify "future" transitions that are not active yet (their transition time has not yet expired). In fact, the update will fail if: - a creation/update job is pending or running already. In this case, 503 is returned. The update can be re-attempted later. - the transition is active already (e.g. transition time in the past). In this case, a 400 error is returned: the operation is prevented because modifying an active transition would break running streams. If you really want to update an active transition and possibly break playout, you can do so by forcing the operation with the `force` query parameter. Use this with extreme caution. NOTICE: if your intent is to switch the channel to a different content (and keep the existing archive) you should just add another "transition". If instead you need to remove the transition, use the "DELETE" endpoint. See the FAQ to understand how this may affect running streams.