Daily recording

Cloud recording for Daily voice sessions — retrieval, storage integration, and troubleshooting.

How recording works

Daily rooms created by Breeze Buddy have cloud recording enabled by default. Recording starts automatically when participants join and captures all audio tracks server-side — no client-side configuration needed.

Recording retrieval flow

After a session ends, Breeze Buddy automatically retrieves and stores the recording:

1. Locate the recording — query GET /recordings?room_name={'{name}'} on the Daily API
2. Get access link — call GET /recordings/{'{id}'}/access-link to obtain a temporary signed download URL
3. Download audio — fetch the audio bytes from the signed URL
4. Upload to cloud storage — store the file in your configured storage provider (GCS or S3)
5. Update lead record — the recording_url field on the lead is updated with the permanent storage URL

Cloud storage configuration

Configure your storage provider via environment variables:

# Google Cloud Storage
RECORDING_STORAGE_PROVIDER=gcs
GCS_BUCKET_NAME=your-recordings-bucket
GCS_CREDENTIALS_FILE=/path/to/service-account.json
# — OR — AWS S3
RECORDING_STORAGE_PROVIDER=s3
S3_BUCKET_NAME=your-recordings-bucket
AWS_ACCESS_KEY_ID=AKIA...
AWS_SECRET_ACCESS_KEY=...
AWS_REGION=us-east-1

Download endpoint

Retrieve the recording for a specific lead via the Breeze Buddy API:

Download Example

const response = await fetch(
  `https://your-api.example.com/agent/voice/breeze-buddy/leads/${leadId}/recording`,
  {
    headers: {
      'Authorization': 'Bearer <your-api-key>'
    }
  }
);
if (response.ok) {
  const blob = await response.blob();
  const url = URL.createObjectURL(blob);
  const audio = new Audio(url);
  audio.play();
} else {
  console.error('Recording not available:', response.status);
}

cURL Example

curl -H "Authorization: Bearer <your-api-key>" \
  -o recording.mp4 \
  https://your-api.example.com/agent/voice/breeze-buddy/leads/{lead_id}/recording

Recording in the lead lifecycle

The recording URL is stored on the lead record once processing completes:

{
  "lead_id": "uuid-of-the-lead",
  "status": "FINISHED",
  "call_id": "room-abc123",
  "recording_url": "https://storage.googleapis.com/your-bucket/recordings/room-abc123.mp4",
  "duration_seconds": 142,
  "outcome": "appointment_confirmed"
}

Troubleshooting