Skip to main content
POST
Batch delete alert rules

Restrictions

Usage

  • IDs are processed in order and the call stops at the first error; rules deleted before the error stay deleted, so fix the cause and re-send the remaining IDs.
  • IDs that do not exist are skipped without error. Each deleted rule’s active alerts are cleared.
  • ids must contain at least one ID. For every rule, the caller must be able to manage its 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.
  • Every call is recorded in the account audit log. Don’t put secrets in request fields.

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
ids
integer<uint64>[]
required

IDs of the alert rules to delete; must contain 1 to 100 IDs. Get them from POST /monit/rule/list/basic.

Required array length: 1 - 100 elements

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

Empty response on success.