Skip to main content
POST
Get rule counts by channel

Restrictions

Usage

  • Only rules with a non-empty channel_ids are counted; a rule routed to several spaces is counted once under each of them.
  • When a space ID cannot be resolved to a name, the ID (as a string) is used as the key. Spaces that share the same name are merged into one key.
  • Returns an empty object {} when no rule routes to a space.

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

No parameters required.

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

Map of channel name to rule count. Unresolved channel IDs appear as stringified IDs.