delete · alerts:write

Delete an alert rule

Notifications stop immediately. Mentions are unaffected.

WriteDestructiveIdempotent

REST

delete/api/v1/alerts/{id}
curl "https://herculradar.com/api/v1/alerts/:id" \
  --request DELETE \
  --header "Authorization: Bearer hr_live_…"

MCP

Tool name delete_alert. It takes the same input and returns the same { data, meta } envelope as REST, because both call the same function.

Permanently remove an alert rule. Notifications stop immediately.

Parameters

idrequiredstringAlert id

Response

{
  "data": {
    "deleted": true,
    "id": "uuid"
  },
  "meta": {
    "capability": "delete_alert",
    "requestId": "req_9f2b4a8c1d0e",
    "idempotencyReplayed": false,
    "docs": "https://herculradar.com/docs/reference/delete_alert"
  }
}

Authorization

Requires the alerts:write scope. A credential without it gets 403 FORBIDDEN. Resources in projects the credential cannot reach answer 404 NOT_FOUND rather than 403, so ids cannot be probed across tenants.

Send an Idempotency-Key header. A completed response is replayed for 24 hours, so a retry after a timeout cannot create a duplicate.