Skip to main content
POST
Grant role to members

Restrictions

Usage

  • Every ID in member_ids must be a member of the account, with no duplicates; otherwise the call returns 400 and nobody is changed.
  • role_id must be a built-in role or a custom role that has not been deleted (disabled roles are accepted, but grant no permissions until enabled); otherwise the call returns 400.
  • 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.
  • Members who already hold the role keep it unchanged.
  • 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

Request to grant or revoke a role from members.

member_ids
integer<uint64>[]
required

IDs of the members to grant the role to or revoke it from (from POST /member/list). All must be members of the account; duplicates are rejected.

role_id
integer<uint64>
required

Role ID to grant or revoke. 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 object returned on success for operations with no meaningful payload.