From d760aaabddd17d8fce40387951f6dba1ecf69eb2 Mon Sep 17 00:00:00 2001 From: dhruva Date: Sat, 21 Nov 2026 00:58:13 +0000 Subject: [PATCH] docs: expand web video recording details Co-Authored-By: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com> --- fern/assistants/call-recording.mdx | 31 ++++++++++++++++++++++++++++++ 1 file changed, 31 insertions(+) diff --git a/fern/assistants/call-recording.mdx b/fern/assistants/call-recording.mdx index bd653f072..50f87ee90 100644 --- a/fern/assistants/call-recording.mdx +++ b/fern/assistants/call-recording.mdx @@ -207,6 +207,37 @@ Configure different types of artifacts with these options: For separate recording in your own Twilio account, see [Twilio outbound transport settings](/phone-numbers/import-twilio#outbound-transport-settings). +## Video recording + +Set `artifactPlan.videoRecordingEnabled` to `true`, or enable **Video Recording** in the assistant's Advanced settings. It defaults to `false` and applies only to web calls using Daily, not phone or Vapi WebSocket calls. After the call ends, find the video URL at `call.artifact.videoRecordingUrl`. + +Video recording is disabled if the organization or any participating assistant has Zero Data Retention (ZDR) or PCI enabled. Daily video recordings use Vapi's storage, so adding custom storage does not enable video recording for those calls. + +### Choose who starts recording + +Set `videoRecordingStartMode` at the top level of the `POST /call/web` creation request, not inside `artifactPlan`. It only applies when video recording is enabled: + +| Mode | Behavior | +| --- | --- | +| `client` (default) | Recording starts when the web client joins. The returned meeting token can start it automatically; older clients can use client-initiated recording. | +| `server` | Vapi starts recording once when the user first joins, so starting does not depend on the client's connection. The returned `transport.callToken` does not start recording, and your client must not start it separately. | + +For example, create a web call using a stored assistant and enable server-started recording for that call: + +```json +{ + "assistantId": "ASSISTANT_ID", + "assistantOverrides": { + "artifactPlan": { + "videoRecordingEnabled": true + } + }, + "videoRecordingStartMode": "server" +} +``` + +In `server` mode, if Vapi cannot set up recording, the response has no `transport.callToken`. If starting recording fails during the call, the client is notified. There is no automatic fallback to a client start. + ## Storage Configuration