Skip to main content
POST
Update member roles

Restrictions

Usage

  • An empty or omitted role_ids assigns the built-in Viewer role (8).
  • Role IDs that do not exist are dropped; if none of the given IDs exist, the member ends up with no roles.
  • Members provisioned through SSO cannot be changed while the SSO configuration marks them non-editable or the account has no active SSO configuration; the call returns 400.
  • Every call is recorded in the account audit log. Don’t put secrets in request fields.

Authorizations

app_key
string
query
required

APP Key created in the Flashduty console under My → APP Key. Send it as the app_key query parameter or in the Fd-App-Key request header. Its effective access is the intersection of the key's permission scope and the creator's current role permissions. Keep it secret.

Body

application/json

Update member roles request

member_id
integer<uint64>
required

ID of the member whose roles change (from POST /member/list).

role_ids
integer<uint64>[]

New role ID set; replaces the member's existing roles entirely (not additive). Get IDs from POST /role/list.

Response

Success

Success response envelope. On every 2xx response, request_id identifies the call (also mirrored in the Flashcat-Request-Id header) and data holds the endpoint-specific payload. Failure responses use a different shape — see ErrorResponse.

request_id
string
required

Unique ID for this request. Mirrored in the Flashcat-Request-Id response header. Include it when reporting issues.

Example:

"01HK8XQE3Z7JM2NTFQ5YJ8P9R4"

data
object

Empty response