Skip to main content
POST
Handler for POST /livekit/participant/mute endpoint
Mutes or unmutes a participant’s published track. Access is authorized via metadata.auth_id check.

Authorization

Room names are used exactly as provided. No prefixing or modification is applied.

Request

Requires:
  • room_name - The LiveKit room where the participant is connected
  • participant_identity - The identity of the participant whose track to mute
  • track_sid - The session ID of the track to mute/unmute
  • muted - true to mute, false to unmute

Error responses

Authorizations

Authorization
string
header
required

Authentication token for protected endpoints. Can be provided as Authorization: Bearer <token> or ?api_key=<token>. Required when AUTH_REQUIRED is enabled.

Body

application/json

Request body for muting/unmuting a participant's track

Example

muted
boolean
required

True to mute, false to unmute

Example:

true

participant_identity
string
required

The identity of the participant whose track to mute

Example:

"user-alice-456"

room_name
string
required

The LiveKit room name where the participant is connected

Example:

"conversation-room-123"

track_sid
string
required

The session ID of the track to mute/unmute

Example:

"TR_abc123"

Response

Track muted/unmuted successfully

Response for a successful mute/unmute operation

Example

muted
boolean
required

Current muted state

Example:

true

participant_identity
string
required

The identity of the participant

Example:

"user-alice-456"

room_name
string
required

The room name

Example:

"conversation-room-123"

track_sid
string
required

The session ID of the track

Example:

"TR_abc123"