Skip to main content
POST
/
monit
/
store
/
ruleset
/
list
List rulesets
curl --request POST \
  --url 'https://api.flashcat.cloud/monit/store/ruleset/list?app_key=' \
  --header 'Content-Type: application/json' \
  --data '
{
  "type_ident": "prometheus"
}
'
{
  "request_id": "01HK8XQE3Z7JM2NTFQ5YJ8P9R4",
  "data": [
    {
      "id": 1,
      "type_ident": "prometheus",
      "note": "CPU usage alerts",
      "open_flag": 2,
      "creator_account_id": 10023,
      "creator_id": 80011,
      "creator_name": "Alice",
      "created_at": 1710000000,
      "updated_at": 1712000000
    }
  ]
}

​
Restrictions

AspectValue
Rate limits1,000 requests/minute; 50 requests/second per account
PermissionsRule Repository Read (monit)

​
Usage

  • A ruleset is visible if its open_flag is 2 (public), if the current user is the creator (open_flag=0), or if it belongs to the same account (open_flag=1).
  • The list does not include the payload field. Call /monit/store/ruleset/info to get the full ruleset content.

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

Filter rulesets by datasource type.

​
type_ident
string
required

Datasource type identifier to filter by, e.g. prometheus.

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

Rulesets accessible to the current user. The payload field is omitted.