> ## Documentation Index
> Fetch the complete documentation index at: https://docs.tavus.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Bring Your Own Daily Room

> Supply a Daily room you created on your own Daily account so the Tavus replica joins your room instead of a Tavus-managed one.

> [!NOTE]
>
> This page is shared with customers under direct enablement. Bring Your Own Daily Room is an enterprise feature. Reach out to your Tavus account team before using it in production.

## Overview

By default, Tavus creates a Daily room when you call [`POST /v2/conversations`](https://docs.tavus.io/api-reference/conversations/create-conversation). The response includes a `conversation_url` on the `tavus.daily.co` domain.

With **Bring Your Own Daily Room**, you create the Daily room yourself (on your own Daily account and subdomain) and pass its URL when creating the conversation. Tavus starts the replica and joins **your** room. The `conversation_url` in the response is the URL you supplied.

This is useful when you need:

* Your own Daily subdomain (for example `yourcompany.daily.co`) instead of `tavus.daily.co`
* Your own Daily API key to call Daily REST APIs against the room (for example [`send-app-message`](https://docs.daily.co/reference/rest-api/rooms/send-app-message))
* Direct control over Daily room settings on rooms you create

Tavus does not share API keys for Tavus-managed Daily rooms. BYO Daily Room is the supported way to get that level of control.

This is separate from [Private Rooms](https://docs.tavus.io/sections/conversational-video-interface/conversation/customizations/private-rooms.md), which adds a Tavus `meeting_token` for joining a Tavus-created room with `require_auth: true`.

## Prerequisites

1. A [Daily](https://www.daily.co/) account with a configured subdomain.
2. A Daily room URL on that subdomain, created through Daily's API or dashboard.
3. If the room is private, a Daily meeting token with permission for the replica to join. Generate this with your Daily API key.

## Request fields

Pass both fields inside `properties` on [`POST /v2/conversations`](https://docs.tavus.io/api-reference/conversations/create-conversation):

| Field | Type | Required | Description |
| - | - | - | - |
| `properties.daily_room` | string | optional | Optional. URL of a Daily room you created yourself (bring-your-own room). If omitted, Tavus creates a Daily room when the conversation is created. If set, the replica joins this room instead. |
| `properties.daily_token` | string | optional | Optional. Daily meeting token the replica uses to join your `daily_room`. If the Daily room is public, you may omit this. Omit when Tavus creates the Daily room (no `daily_room`). |

## Create a conversation

```shell cURL theme={null}
curl --request POST \
  --url https://tavusapi.com/v2/conversations \
  --header 'Content-Type: application/json' \
  --header 'x-api-key: <api_key>' \
  --data '{
  "replica_id": "r4b03c679d42",
  "persona_id": "p22f53b7b4b9",
  "properties": {
    "daily_room": "https://your-subdomain.daily.co/your-room",
    "daily_token": "<daily_meeting_token_if_room_is_private>"
  }
}'
```

For a **public** Daily room, omit `daily_token`:

```json theme={null}
{
  "replica_id": "r4b03c679d42",
  "persona_id": "p22f53b7b4b9",
  "properties": {
    "daily_room": "https://your-subdomain.daily.co/your-room"
  }
}
```

> [!NOTE]
>
> Replace `<api_key>` with your actual API key. You can generate one in the [PAL Maker](https://maker.tavus.io/dev/api-keys).

The response `conversation_url` matches the `daily_room` you passed:

```json theme={null}
{
  "conversation_id": "c123456789",
  "conversation_url": "https://your-subdomain.daily.co/your-room",
  "status": "active"
}
```

Join the conversation the same way you would with a Tavus-issued URL: open `conversation_url` in a browser or pass it to the Daily SDK.

## Validation

The API returns `400` when:

| Condition | Error |
| - | - |
| `properties.daily_token` is set without `properties.daily_room` | `properties.daily_token requires properties.daily_room to also be provided.` |
| `properties.daily_room` is not a valid Daily URL | `properties.daily_room must be a valid Daily room URL (https://<domain>.daily.co/<room>).` |
| `meeting_url` is set together with BYO or LiveKit room fields | `meeting_url is mutually exclusive with BYO-daily and LiveKit rooms` |

Rules enforced by the API:

* `daily_room` must use `https://` and must contain `.daily.co/`.
* `daily_token` requires `daily_room`.
* Do not combine `properties.daily_room` or `properties.daily_token` with `meeting_url`, `properties.livekit_ws_url`, or `properties.livekit_room_token` on the same request.

## Ending the conversation

Call [`POST /v2/conversations/{conversation_id}/end`](https://docs.tavus.io/api-reference/conversations/end-conversation) when the session is done. Tavus shuts down the replica and billing for that conversation.

Because Tavus does not own your Daily room, Tavus does not delete the room or manage its lifecycle. You are responsible for creating, configuring, and tearing down Daily rooms on your account.

When you use a Tavus-managed room, Tavus can detect when the room no longer exists. With BYO Daily Room, Tavus relies on participant-leave signals and the end-conversation call instead. If you delete the Daily room while the replica is still connected, shutdown may be delayed until `max_call_duration` is reached. End the conversation through the API first, then delete the room.

## Related docs

* [Private Rooms](https://docs.tavus.io/sections/conversational-video-interface/conversation/customizations/private-rooms.md) for Tavus-managed rooms with `require_auth`
* [Interactions Protocol](https://docs.tavus.io/sections/conversational-video-interface/interactions-protocols/overview.md) for Tavus app messages during a conversation (works alongside BYO rooms; use Daily's APIs when you need to push messages with your own Daily API key)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.