Deletes the video, every clip made from it, and the stored files they own, then credits the freed bytes back to the workspace storage quota. This cannot be undone.
Authorization
bearerAuth An API key created under Settings > API & Webhooks. Keys start with sf_live_.
In: header
Path Parameters
Response Body
application/json
application/json
application/json
curl -X DELETE "https://example.com/videos/string"{ "data": { "ok": true, "deletedClips": 4, "freedBytes": 91234816 }}Make a clip or variation POST
Creates a new video from this one, pointing back at it through `parentVideoId`. `regenerate: true` (charging credits) writes the next episode of a faceless video: a new script on the same theme, a new voice-over and new visuals. On other video types it only writes a new title and caption, and the scenes, actor and narration are reused. `render: true` queues the render as soon as the clip is ready. On an automation, `regenerate: true` is refused with `warning-automation-needs-prompt` when the automation has nothing to write from (no `scriptPrompt` and no `prompt`), since the clip would repeat its first video. The editor's pipeline guards (nothing failed, nothing already waiting to publish) are deliberately off here: an integration builds its own flow and is not looking at the publishing pipeline view.
Get a video GET
One video with its brief, theme config, media URLs and both job documents. The content arrays are excluded by default because they dominate the payload; opt into the ones you need with `include`.