Skip to main content
POST
Delete Automation rule

Restrictions

Usage

  • Deleting a rule also removes its schedule, HTTP POST, On-call incident, and war room triggers; the HTTP POST trigger token stops working.
  • Manage rights: a personal rule (team_id=0) can be managed only by its owner; a team rule only by members of that team. Account owners and admins get no exemption and must join the team. Others get 403.
  • While another update, delete, or manual run of the same rule is in progress, the call fails with HTTP 423 and code: "RequestLocked"; retry later.
  • Every call is recorded in the account audit log.

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
rule_id
string
required

Rule ID, from the list returned by POST /safari/automation/rule/list.

Response

Success

Standard response envelope used by every Flashduty public API. On success data contains the endpoint-specific payload and error is absent. On failure error is present and data is absent. request_id is always present and is also mirrored in the Flashcat-Request-Id response header.

request_id
string
required

Unique ID for this request. Mirrored in the Flashcat-Request-Id header. Include it when reporting issues.

Example:

"01HK8XQE3Z7JM2NTFQ5YJ8P9R4"

error
object

Error payload inside the response envelope. Present only on non-2xx responses.

data
null

Not returned on success; the body carries only request_id.