Update ruleset

Update the note, sharing flag, and payload of an existing ruleset.

POST /monit/store/ruleset/update

Update ruleset

cURL

curl --request POST \
  --url 'https://api.flashcat.cloud/monit/store/ruleset/update?app_key=' \
  --header 'Content-Type: application/json' \
  --data '
{
  "id": 1,
  "note": "Updated CPU alerts",
  "open_flag": 2,
  "payload": "[{\"prom_ql\":\"rate(cpu_usage[5m]) > 0.9\"}]"
}
'

200

{
  "request_id": "01HK8XQE3Z7JM2NTFQ5YJ8P9R4",
  "data": {
    "id": 1,
    "note": "Updated CPU alerts",
    "open_flag": 2,
    "updated_at": 1712100000
  }
}

Restrictions

Aspect	Value
Rate limits	1,000 requests/minute; 50 requests/second per account
Permissions	Rule Repository Manage (monit)

Usage

• 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

Parameters for updating a ruleset.

id · integer<uint64> · required

Ruleset ID to update.

note · string · required

New description.

payload · string · required

New JSON string of alert rule definitions.

open_flag · enum<integer>

New sharing scope. 0 = private, 1 = account-shared, 2 = public.

Available options: 0, 1, 2

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

A rule repository ruleset.

Show child attributes