Turn a finished livestream into a VOD. The server concatenates the MUXL segments it recorded for the livestream(s) into a single content blob, derives the playback sidecars, and publishes the place.stream.media.track records. By default it leaves a draft VOD the streamer publishes later via place.stream.vod.publishDraft; with publish set it publishes the place.stream.video record as soon as the VOD is finalized. The caller must be the streamer, or a moderator they have granted livestream.manage; every record is written with the streamer's session.
Request Body required
Section titled “Request Body required ”object
AT-URI of the place.stream.livestream record to finalize into a VOD. Either this or livestreams is required.
Several livestream records whose recordings make up one VOD: a streamer who started a new record mid-stream splits the recording across them. Recordings are concatenated in the records’ creation order, whatever order they are listed in. All must belong to one streamer.
Title of the video record; the first livestream’s title when empty.
Description of the video record.
Publish the place.stream.video record as soon as the VOD is finalized, instead of leaving a draft.
Also end any of the livestream records that were never stopped, so the streamer’s page stops reading as live.
Responses
Section titled “ Responses ”Success
object
Identifier for the finalize job. Retained for backwards compatibility; the draft flow no longer requires the client to poll getUploadStatus.
The ats:// URI of the draft VOD created for this finalize, when publish is not set. The draft reaches status ‘ready’ when processing completes.
The livestream records the VOD is made of, in recording order.
How many recorded objects will be concatenated.
Livestream records that are now ended (already, or by endLivestream).
Bad Request