Skip to main content
POST
/
role
/
member
/
revoke
Revoke role from members
curl --request POST \
  --url 'https://api.flashcat.cloud/role/member/revoke?app_key=' \
  --header 'Content-Type: application/json' \
  --data '
{
  "member_ids": [
    80011
  ],
  "role_id": 150
}
'
{
  "request_id": "01HK8XQE3Z7JM2NTFQ5YJ8P9R4",
  "data": {}
}

Documentation Index

Fetch the complete documentation index at: https://docs.flashcat.cloud/llms.txt

Use this file to discover all available pages before exploring further.

​
Restrictions

AspectValue
Rate limits1,000 requests/minute; 50 requests/second per account
PermissionsRoles Manage (organization)

​
Usage

  • Members who don’t 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.