Skip to main content
POST
Get rule counter time series

Restrictions

Usage

  • Each item is a historical snapshot: num is the total number of alert rules in the account (enabled and disabled) at clock (Unix timestamp in seconds).
  • A snapshot is recorded roughly every 12 hours (an hourly job adds one when none exists in the last 12 hours). All snapshots are returned oldest first; the array is empty until the first snapshot is recorded.

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[]

Historical rule-count samples ordered by clock ascending.