efd9e4bc659f
Rtvi Connect
Headers
Request body
Single-character UUID, optionally followed by -draft, -latest, or a major.minor[.patch] version. Roster entries currently accept bare UUIDs only.
Client-provided grouping key used to deterministically place participants into the same shared session/room.
Client-generated idempotency key for one logical connection attempt. Retries with the same key and payload replay the original response.
Example request
{
"character_id": "00000000-0000-4000-8000-000000000001"
}Response
Successful Response
Unique session token
Server-side request trace ID for correlating client events, logs, telemetry, and session records for this /connect request
Interaction session id
URL of the room to connect to
Room name (only for LiveKit transport)
Authentication token for the room
The end_user_id associated with this session when provided
Metadata associated with the end user