Skip to API content
TalkLabs API Docs v3
Recipes
POST User sessions & access

Set user permissions (not implemented)

This endpoint is present in the API contract but does not currently apply permission changes.

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

This endpoint is present in the API contract but does not currently apply permission changes.

Do not use it in production. Use Create or Update User to change the stored role, or Set a user role for the supported role-change operation.

Request

Parameters

Values in the path and query string.

appid path
string TalkLabs ID required

The application the user belongs to.

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

The user the permissions would apply to.

Example: u-8842
Request

JSON body

Send as application/json.

roles
AccessRole[]

Required. An array of granular permission records to apply to the user, e.g. admin on one specific room while holding the "user" role at the application level. NOTE: as of this writing the server action that binds this form POST .../setroles does not yet apply it see that action's remarks.

Request example
{
  "roles": [
    "<roles>"
  ]
}
Response

Status codes

Every JSON response uses the API result envelope.

200 OK: request accepted, but no permission change is actually applied see NOTE above . ApiResult
400 BadRequest: the request body was not provided. ApiResult
403 Forbidden: request is not authorized with a valid token. 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.