Welcome to the new Daily Docs. Please let us know what you think.

Configuration

A cloud recording object represents a single saved recording, and has the following properties:

id
string

A unique, opaque id for this object. You can use this id in API calls, and in paginated list operations.

room_name
string

The name of the room.

start_ts
integer

When the recording started. This is a unix timestamp (seconds since the epoch).

status
string
Options: "finished","in-progress","canceled"
max_participants
integer

The maximum number of participants that were ever in this room together during the meeting session that was recorded.

duration
integer

How many seconds long the recording is, approximately. This property is not returned for recordings that are in-progress.

share_token
string

A re-settable id that can be used to allow direct download of a recording file. In general, you probably shouldn't use this. Please see below.

Download links and share tokens

Please note that our cloud recording storage is intended for archiving, not for streaming. The .webm file format is not ideal for live streaming. You can't seek through a .webm file in an in-browser video player, for example. And .webm support on platforms other than Chrome is not very good.

The .webm files for cloud recordings are stored on Amazon S3. To make the .webm file available for download, you will usually create a time-limited access link for the recording.

For convenience in scripts, or if your use case absolutely requires a long-lived download link, you can also use the recording object's share_token to download the .webm file. Use cases with this requirement are rare, and generally aren't a good fit for the engineering and cost trade-offs we've made with regard to how recordings are encoded and stored. If you have questions about this please contact us.