Room management endpoints are under /api/room/. All endpoints require authentication.

Overview

Endpoints

Create Room

Create a new meeting room. The authenticated user becomes the room admin.

POST /api/room/create

Headers: Authorization: Bearer <accessToken>

Request Body:

{
  "name": "team-standup",
  "isPublic": true,
  "mode": "standard",
  "settings": {
    "allowChat": true,
    "allowVideo": true,
    "allowAudio": true,
    "requireApproval": false,
    "e2ee": false
  }
}

Note: The name field is optional. If omitted or empty, the server will auto-generate a random URL-safe name in the format xxx-xxxx-xxx (e.g. bkf-qmzl-rja).

Room Name Rules:

Room names appear in the URL as https://bedrud.xyz/m/NAME, so they must be URL-safe:

Response (200):

{
  "id": "uuid",
  "name": "team-standup",
  "createdBy": "user-uuid",
  "isActive": true,
  "isPublic": true,
  "maxParticipants": 0,
  "settings": {
    "allowChat": true,
    "allowVideo": true,
    "allowAudio": true,
    "requireApproval": false,
    "e2ee": false
  },
  "livekitHost": "wss://lk.bedrud.xyz",
  "mode": "standard"
}

Fields

Join Room

Join an existing room and receive a LiveKit token for media connection.

POST /api/room/join

Headers: Authorization: Bearer <accessToken>

Request Body:

{
  "roomName": "team-standup"
}

Response (200):

{
  "id": "uuid",
  "name": "team-standup",
  "token": "eyJ...",
  "createdBy": "user-uuid",
  "adminId": "user-uuid",
  "isActive": true,
  "isPublic": true,
  "maxParticipants": 20,
  "expiresAt": "2026-02-16T12:00:00Z",
  "settings": { ... },
  "livekitHost": "wss://lk.bedrud.xyz",
  "mode": "standard"
}

The token is a signed LiveKit access token. Use it to connect to the LiveKit server via WebSocket:

import { Room } from 'livekit-client';
 
const room = new Room();
await room.connect(livekitUrl, token);

List Rooms

Get a list of rooms the user has created.

GET /api/room/list

Headers: Authorization: Bearer <accessToken>

Response (200):

[
  {
    "id": "uuid",
    "name": "team-standup",
    "createdBy": "user-uuid",
    "isActive": true,
    "maxParticipants": 20,
    "expiresAt": "2026-02-16T12:00:00Z",
    "settings": { ... },
    "mode": "standard",
    "relationship": "creator"
  }
]

Kick Participant

Remove a participant from the room. Only the room admin can do this.

POST /api/room/:roomId/kick/:identity

Headers: Authorization: Bearer <accessToken>

Response (200):

{
  "status": "success"
}

Mute Participant

Mute a participant’s microphone. Only the room admin can do this.

POST /api/room/:roomId/mute/:identity

Headers: Authorization: Bearer <accessToken>

Response (200):

{
  "status": "success"
}

Disable Participant Video

Turn off a participant’s camera. Only the room admin can do this.

POST /api/room/:roomId/video/:identity/off

Headers: Authorization: Bearer <accessToken>

Response (200):

{
  "status": "success"
}

Admin Controls

Room admin actions (kick, mute, video off) are only available to the user who created the room (adminId). Attempting these actions as a non-admin returns a 403 error.

Permissions Matrix

Error Responses

All errors follow a consistent format:

{
  "error": "human-readable error message"
}

Create Room Errors

General Errors

See also

• Architecture Overview - data model and meeting connection flow
• API Handlers - how room endpoints are implemented