Skip to content

Deletes alarm rule
Stable

Request

⚠️ Android only.

Permanently deletes an alarm rule identified by its UUID alarm_id. This action is irreversible — the rule, its configuration, and its association with any alert channels are removed immediately. Historical firing data for the rule is also no longer accessible after deletion.

Common use cases

Removing alarm rules that are no longer relevant after a fleet restructure or deployment phase ends

Cleaning up duplicate or misconfigured rules created during setup

Decommissioning monitoring configurations for device groups that have been dissolved

Best practices

Retrieve the rule with GET /v1/enterprise/{enterprise_id}/alarmrules/{alarm_id}/ before deleting to confirm it is the correct rule — this action cannot be undone

If the intent is to stop the rule from firing temporarily rather than permanently remove it, consider using PATCH /v1/enterprise/{enterprise_id}/alarmrules/{alarm_id}/ to set is_active=false instead

Review firing history via GET /alarmrules/{alarm_id}/alarmhistory/ before deleting if the rule's historical trigger data is needed for reporting or auditing purposes — this data will not be recoverable after deletion

Note that deleting an alarm rule does not delete the alert channels it referenced — channels are enterprise-level resources and remain available for use by other rules

Security
esper_cloud_api_apiKey
Path
enterprise_idstringrequired

A UUID string identifying this enterprise.

alarm_idstringrequired

A UUID string identifying the alarm ruleset.

cURL
curl -i -X DELETE \
  'https://api.esper.io/_mock/openapi/v1/enterprise/{enterprise_id}/alarmrules/{alarm_id}/' \
  -H 'Authorization: Bearer <YOUR_TOKEN_HERE>'

Responses

The resource was deleted successfully.

Response
No content