Skip to main content
POST
Get rule audit snapshot

Restrictions

Usage

  • Pass the audit record id (not the rule id) from POST /monit/rule/audits. An unknown ID returns InvalidParameter (alert rule audit not found).
  • content is a JSON string — parse it to get the rule snapshot; its shape depends on the operation that wrote the record (see content below).
  • To read a record, 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. Records of a deleted rule can no longer be read: the call returns InvalidParameter (alert rule not found).

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

Audit record ID — the id of a row returned by POST /monit/rule/audits, not the rule ID. A rule ID is looked up as an audit record ID, which usually returns InvalidParameter (alert rule audit not found) or an unrelated record.

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

An audit record capturing a rule snapshot at a point in time.