Update an alert

curl "https://herculeradar.com/api/v1/alerts/:id" \
  --request PATCH \
  --header "Authorization: Bearer hr_live_…" \
  --header "Content-Type: application/json" \
  --header "Idempotency-Key: $(uuidgen)" \
  --data '{}'

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

Change an alert rule. Only the fields you pass change.

{
  "type": "object",
  "properties": {
    "name": {
      "type": "string"
    },
    "active": {
      "type": "boolean"
    },
    "min_urgency": {
      "type": "integer"
    }
  }
}

{
  "data": {
    "id": "uuid",
    "active": false
  },
  "meta": {
    "capability": "update_alert",
    "requestId": "req_9f2b4a8c1d0e",
    "idempotencyReplayed": false,
    "docs": "https://herculeradar.com/docs/reference/update_alert"
  }
}

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.