Skip to main content
POST
Grant role to members

Restrictions

Usage

  • Up to 100 member IDs per request.
  • Members who already have the role are silently skipped.
  • Every call is recorded in the account audit log. Don’t put secrets in request fields.

Authorizations

app_key
string
query
required

App key issued from the Flashduty console under Account → APP Keys. Required on every public API call. Keep it secret — it grants the same access as the owning account.

Body

application/json

Request to grant or revoke a role from members.

member_ids
integer<uint64>[]
required

Member IDs to grant/revoke the role. Max 100.

role_id
integer<uint64>
required

Role ID to grant or revoke.

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
required

Empty object returned on success for operations with no meaningful payload.