Skip to main content
These pages describe the Training API on dev, where authenticated creation, editing, downloads, revert, and website brand lookup have been tested live. Production availability is not confirmed. Your API service and worker must both run the updated code. See Testing and availability.
GET {API_BASE}/v1/edits/{edit_id}
Both the edit record and its video must be accessible within the key’s scope.

Response

The result can include:
  • video_synced: whether the edit was applied through video sync. False means no new rendered video was applied, for example when no rendered timestamps existed.
  • link: an available video URL; may be null. Do not infer synchronization from the URL alone.
  • changed_scene_numbers, added_scene_numbers, deleted_scene_numbers: planner changes.
  • regenerated_scenes, kept_scenes: rendering outcomes.
  • revert_diff: snapshot changes when reverted.
An edit can finish scene synchronization before the combined MP4 is assembled. If result.link is null, poll video status using video_uuid until is_complete is true and video_url is available. Treat that URL as the video’s current output; a later edit can replace it. Signed Knowlify media URLs expire after one hour, so fetch a fresh status response when needed. Poll about every five seconds, back off on errors, and impose a timeout. Progress is approximate and can skip stages; clients must not depend on seeing every intermediate stage. If the edit waits for approval or clarification, stop polling for completion. Read required_action and take the matching edit action. Automatic plan approval remains the default. A completed edit can be reverted if it meets the snapshot and ordering requirements.