Check stream readiness
What would stop POST /streams//start, changing nothing: ready, and each blocking issue (code, error, suggestion; destinationId when it is about one destination). It checks that quality and framerate are set; that at least one destination is enabled and not archived, supports the stream’s quality, and for YouTube has its broadcast settings (title, made-for-kids) and a connected channel; that the video playlist has items, and that there is an audio playlist when a video in it has no sound; that the playlists’ media fits the stream’s included storage (else set storageBackend to the large tier with PATCH /streams/); and, for a stream that plays a scene, that the scene is published and valid and the stream is at most 1080p60. It does not check credits or YouTube live eligibility (start does), nor whether uploads have finished processing: a playlist only takes completed uploads, and their metadata (see GET /uploads/) need not have arrived yet.
Authorizations
OAuth 2.1 authorization-code flow with PKCE.
Headers
Workspace this request operates in — the workspace id (wksp_…) or the organization id, from GET /workspaces. Required with an API key, which carries no workspace (400 WORKSPACE_REQUIRED without it). With an OAuth token it defaults to the workspace the token was issued for. Responds 403 WORKSPACE_FORBIDDEN when the caller is not a current member, rather than falling back to another workspace.
Path Parameters
Resource identifier.