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 callPOST /v2/conversations. 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 oftavus.daily.co - Your own Daily API key to call Daily REST APIs against the room (for example
send-app-message) - Direct control over Daily room settings on rooms you create
meeting_token for joining a Tavus-created room with require_auth: true.
Prerequisites
- A Daily account with a configured subdomain.
- A Daily room URL on that subdomain, created through Daily’s API or dashboard.
- 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 insideproperties on POST /v2/conversations:
Create a conversation
cURL
daily_token:
Replace
<api_key> with your actual API key. You can generate one in the PAL Maker.conversation_url matches the daily_room you passed:
conversation_url in a browser or pass it to the Daily SDK.
Validation
The API returns400 when:
Rules enforced by the API:
daily_roommust usehttps://and must contain.daily.co/.daily_tokenrequiresdaily_room.- Do not combine
properties.daily_roomorproperties.daily_tokenwithmeeting_url,properties.livekit_ws_url, orproperties.livekit_room_tokenon the same request.
Ending the conversation
CallPOST /v2/conversations/{conversation_id}/end 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 for Tavus-managed rooms with
require_auth - Interactions Protocol 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)

