Update Video

PATCH /v1/videos/:id

Rename a video, move it between projects, or adjust the context used when generating content.

Only these fields are settable. Generated content - subtitles, help articles, exports - comes from the operations that produce it, not from this endpoint.

Path parameters

Parameter	Type	Description
id	string	The video ID

Request body

At least one field is required.

Field	Type	Description
name	string	Display name, 1-200 characters
projectId	string | null	Project folder to file it under. null uncategorizes it.
videoContext	string	What the video shows - steers generated content
companyContext	string	Company or product background used when generating content
subtitleLanguage	string	Language code (see List Languages)

Example

curl -X PATCH https://api.vidocu.ai/v1/videos/vid_abc123 \
  -H "Authorization: Bearer vdo_live_your_key_here" \
  -H "Content-Type: application/json" \
  -d '{"name": "Onboarding - step 3", "projectId": "proj_xyz"}'

Response 200 OK

Returns the updated video, in the same shape as Get Video.

{
  "id": "vid_abc123",
  "projectId": "proj_xyz",
  "name": "Onboarding - step 3",
  "status": "completed",
  "locked": false,
  "lock": null,
  "updatedAt": "2026-08-09T11:02:00.000Z"
}

Renaming the whole package

If the workspace has Naming - keep the package named as one thing switched on, renaming a video also renames its help article and its linked training module, in the same request. Nothing extra to send: it follows from name.

• A locked module is skipped and the rename still succeeds. A lock is irreversible, and an approved round is locked, so this is how frozen content stays frozen.
• A title someone edited by hand is still overwritten by a rename - the setting governs generation and rename, and a rename is an explicit act.
• Knowledge Base articles are not renamed. A published article's title drives its public slug, and renaming a video must not change a URL people have already linked to.

With the setting off (the default), name touches the video only.

Locked videos

A locked video can still be moved between projects - filing isn't a content change. Any other field returns 423 Locked naming the fields you tried to change.

{
  "error": {
    "code": "locked",
    "message": "This video is locked by Dana Levi on 2026-08-01T09:14:00.000Z and can't be changed. Unlock it before you change name."
  }
}

Errors

Status	Code	Cause
400	validation_error	No fields given, or a value failed validation
401	authentication_error	Invalid or missing API key
403	insufficient_role	The workspace role behind the token can't edit videos
404	not_found	Video doesn't exist, belongs to another workspace, or projectId names a folder outside it
423	locked	The video is locked and the change isn't filing