Recording events

Recording events notify your application when a call recording has been completed and is ready for retrieval.

recording.completed

Fired when recording is stopped via the record/stop command. The event includes a URL where the recording can be accessed and the total recording duration.

Note

The command_uid in this event matches the command_uid from the original record/start request, not the record/stop request. This lets you correlate the completed recording with the start command that initiated it.

Payload schema

Field	Type	Description
event	string	Always "recording.completed". required
session_uuid	string	Unique session identifier. required
recording_url	string	URL where the recording can be accessed. required
duration	integer	Recording duration in seconds. required
command_uid	string	The command_uid from the record/start request that initiated the recording. required

{
  "event": "recording.completed",
  "session_uuid": "acW68-f47ac10b-58cc-4372-a567-0e02b2c3d479",
  "recording_url": "https://recordings.example.com/rec-2026-03-21-abc123.wav",
  "duration": 62,
  "command_uid": "rec-start-001"
}

Caution

URL validity: The recording_url is fetchable for 24 hours after this webhook fires. After that window the URL returns 404 Not Found. Applications that need longer-lived audio must download the WAV within 24 hours and store it themselves. See Recording lifecycle / URL validity for the full contract.

Recording lifecycle

A typical recording flow produces the following events:

1. record/start command → command.result (immediate, success: true).
2. record/stop command → command.result (immediate, success: true) + recording.completed.

Triggered by

These events are produced by the following endpoints:

• recording.completed — record/stop (uses the command_uid from the original record/start).