Skip to main content
POST
/
monit
/
rule
/
info
Get alert rule detail
curl --request POST \
  --url 'https://api.flashcat.cloud/monit/rule/info?app_key=' \
  --header 'Content-Type: application/json' \
  --data '{
  "id": 50001
}'
{
  "request_id": "01HK8XQE3Z7JM2NTFQ5YJ8P9R4",
  "data": {
    "id": 50001,
    "folder_id": 100,
    "name": "CPU High",
    "ds_type": "prometheus",
    "ds_list": [
      "prometheus*"
    ],
    "enabled": true,
    "cron_pattern": "* * * * *",
    "channel_ids": [
      20001
    ]
  }
}

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
PermissionsAlerting Rules Read (monit)

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
​
id
integer<uint64>
required

Rule ID.

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

Full alert rule returned by the info endpoint. All server-assigned fields are guaranteed present.