Enable a role

Re-enable a previously disabled custom role.

POST /role/enable

Enable a role

cURL

curl --request POST \
  --url 'https://api.flashcat.cloud/role/enable?app_key=' \
  --header 'Content-Type: application/json' \
  --data '{
  "role_id": 150
}'

200

{
  "request_id": "01HK8XQE3Z7JM2NTFQ5YJ8P9R4",
  "data": {}
}

Restrictions

Aspect	Value
Rate limits	1,000 requests/minute; 50 requests/second per account
Permissions	Roles Manage (organization)

Usage

• Only custom roles can be enabled/disabled. Built-in roles always remain enabled.
• 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

role_id · integer<uint64> · required

Role ID.

Response

200

application/json

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.