Skip to API content
TalkLabs API Docs v3
Recipes
POST Moderate users

Mute User

A muted user is in a read only state.

POST /api/v3/{appid}/user/users/{userid}/mute

A muted user is in a read-only state. The muted user can join chat rooms and observe but cannot communicate. This method applies mute on the global level (applies to all talk contexts). You can optionally specify an expiration time. If the expiration time is specified, then each time the shadow banned user tries to send a message the API will check if the shadow ban has expired and will lift the ban.

  • userid: (required) The applicaiton provided userid of the user to ban
  • applyeffect: (required) true or false. If true, user will be set to muted state. If false, will be set to non-banned state.
  • expireseconds: (optional) Duration of mute in seconds. If specified, the mute will be lifted when this time is reached. If not specified, mute effect remains until explicitly lifted. Maximum seconds is a double byte value.
Request

Parameters

Values in the path and query string.

appid path
string TalkLabs ID required

The TalkLabs application ID assigned to your account.

Example: your-app-id
userid path
string customer-defined required

The customer defined user ID from your application or identity system.

Example: u-8842
Request

JSON body

Send as application/json.

applyEffect
boolean required
expireSeconds
integer · int32
Request example
{
  "applyEffect": true
}
Response

Status codes

Every JSON response uses the API result envelope.

200 OK ApiResult
400 Bad Request ApiResult
403 Forbidden ApiResult
500 Internal Server Error ApiResult
Search all 118 endpoints Try “join room”, “moderate”, or “POST”.
Request environment

Connect your application

These values fill request examples and the API console. They stay in this browser tab and are never sent to TalkLabs until you run a request.

Credentials are stored in sessionStorage, not in cookies or analytics.