Recording
A guide on how to record your Daily Bot calls
When starting a bot, you can configure recording settings to capture the conversation. These settings allow you to specify the recording type and storage location.
Recording Types
There are two types of recordings available: cloud recordings and raw tracks.
Cloud Recordings
Cloud recordings are the default recording type and provide a simple way to record your calls. The recording will be stored in Daily’s cloud storage or optionally in your own custom S3 bucket.
Raw Tracks
Raw tracks provide separate audio files for each participant in the call, giving you more flexibility for post-processing. To record with raw tracks, you need to specify your own custom S3 bucket for storage.
Recording storage
Recording storage can be configured in two ways: Daily’s cloud storage or your own S3 bucket.
Daily Cloud Storage
By default, your recordings will be stored in Daily’s cloud storage. You can access your recordings through the REST API. For more information on how to do that, see the API reference for getting recordings.
Custom S3 Bucket Configuration
You can configure your own S3 bucket to store recordings by providing the recordings_bucket
settings:
Need help setting up your S3 bucket? Check out Daily’s S3 bucket configuration guide.
You’ll need your Daily domain name, which can be found in the Daily Bots Dashboard: Account (top right corner) > Manage account > Daily Account.
Required Bucket Settings
Property | Description |
---|---|
assume_role_arn | The ARN of the IAM role that Daily will assume to access your bucket |
bucket_name | The name of your S3 bucket |
bucket_region | The AWS region where your bucket is located |
Optional Bucket Settings
Property | Description |
---|---|
allow_api_access | Enable API access to recordings in your bucket |
allow_streaming_from_bucket | Enable streaming of recordings directly from your bucket |
Example /bots/start
Request with Recording
Here’s a simple example of starting a bot with recording enabled:
Make sure your S3 bucket has the appropriate permissions and that the provided IAM role has the necessary permissions to write to the bucket.