List video and edit jobs

These routes require the updated API service. Check Testing and availability before using them in production.

Use your API key to list recent jobs in its workspace. Each list returns short summaries. Use an identifier with video status or edit status for full progress.

Method	Route	Contents
GET	`/v1/videos`	Accessible Training videos
GET	`/v1/edits`	Accessible Training edits submitted through the API
GET	`/v1/marketing/videos`	Accessible Marketing videos
GET	`/v1/marketing/edits`	Accessible Marketing edits submitted through the API

curl --fail-with-body "$API_BASE/v1/edits?limit=20" \
  -H "X-API-Key: $KNOWLIFY_API_KEY"

Set limit from 1 to 100. The default is 20. To read another page, pass the returned next_cursor as cursor. A null cursor means there are no more pages.

{
  "items": [{
    "edit_id": "11111111-1111-4111-8111-111111111111",
    "video_uuid": "22222222-2222-4222-8222-222222222222",
    "status": "awaiting_approval",
    "requires_action": true,
    "created_at": "2026-09-30T10:00:00Z",
    "updated_at": "2026-09-30T10:01:00Z"
  }],
  "next_cursor": null
}

Video items use uuid, status, render_status, requires_action, created_at, and updated_at. Lists do not include the request text, plan, question, or video URL. Deleting a chat removes its jobs from these lists. A status request for a job whose chat was deleted returns 404. The video list uses a saved API-origin marker. Videos created before this update may be absent from the list. You can still check a known video ID with the status route.

Overview

Guides

Endpoints

List video and edit jobs