Rooms and participants

A room is created the moment the first participant joins with a valid token, and closes when the last one leaves. You do not have to create rooms ahead of time, but you can.

From your server

The LiveKit server SDK's room and participant methods work against your tenant with your key: create, list and delete rooms; list, remove and mute participants; send data to a room; update room and participant metadata.

import { RoomServiceClient } from 'livekit-server-sdk';

const svc = new RoomServiceClient('https://acme-7k2q.livecore.cloud', LIVECORE_KEY, LIVECORE_SECRET);
const rooms = await svc.listRooms();
await svc.removeParticipant('show-42', 'user-9');

Names and limits

• Room names are yours. Use whatever your app already uses; they are namespaced to your tenant without you seeing it.
• Your tenant has a cap on concurrent participants and on concurrent rooms. A join that would pass a cap is refused rather than degrading everyone else; someone reconnecting to a room that is already open still gets in. Both numbers are on your Account page; ask us to raise them.
• Webhooks to your server are not offered today. Tell us if your app depends on them.
• One region: Mumbai. Latency from South Asia is excellent; from elsewhere it is what the distance makes it. Dedicated clusters can be placed where your users are.

What you can see live

Your portal's Overview shows the rooms open right now and how many participants are in them, the same figures our own console reads.