Skip to main content
These routes require the updated API service, worker, and database migration. Check Testing and availability before using them in production.
Use the edit_id from edit submission or the edit list. The key must still have access to the edit and its video.

​
Cancel one edit

Cancel a queued edit or an edit that has not started applying changes. Other edits on the video continue. Once apply starts, cancel returns 409. Use revert after an eligible edit completes.
The response returns the edit and video IDs with status: "cancelled". A running worker releases its slot when it exits.

​
Retry a failed edit

Retry only an edit whose status is error. An early failure starts a new edit turn. A failed apply reuses its saved scene changes and edit ID. Read the returned edit_id before polling again.
The response sets retry_mode to new_turn or resume_apply. A new turn returns a new edit_id.

​
Approve a saved plan

Set approval_mode: "manual" when you submit the edit. Wait for status: "awaiting_approval". Read required_action.plan, then approve that saved plan.
An outdated plan returns 409. Automatic approval remains the default when you omit approval_mode.

​
Answer an edit question

When edit status is awaiting_clarification, read required_action.question. Send the missing detail as answer, or cancel the edit. Edit questions do not have a skip action.
The API checks the saved question before continuing. A stale answer returns 409.