Skip to main content
POST
List rule change history

Restrictions

Usage

  • Records are ordered newest first and omit content; read one snapshot with POST /monit/rule/audit/detail.
  • A record is written on every create, full update, field update and move. Deleting a rule writes no record, and the history of a deleted rule can no longer be listed: the call returns InvalidParameter (alert rule not found).
  • The caller must be able to manage the rule’s folder (account owner or admin, creator of the folder or one of its ancestors, or member of the team bound to the folder or an ancestor); otherwise the call returns AccessDenied.

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

Alert rule ID. Obtainable per folder via POST /monit/rule/list/basic.

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

Audit records for a rule, ordered by creation time descending. The content field is omitted.