Webhooks Reference

Listen for real-time infrastructure events and trigger custom business logic across your stack.

How it works

When HealBot detects or resolves an incident, CartNerve sends an HTTP POST request to your configured endpoint. Payloads are JSON-encoded and signed for security.

Supported Events

Event Type	Trigger Condition
incident.detected	Triggered immediately when an anomaly violates the 1.2s detection threshold.
heal.started	Triggered when HealBot identifies a playbook and begins autonomous remediation.
heal.succeeded	Triggered when the health check returns green after an automated action.
heal.failed	Triggered if resolution fails or falls below the 85% confidence threshold.

Example Payload

{
  "id": "evt_9982x",
  "type": "incident.healed",
  "created_at": "2026-03-01T14:20:00Z",
  "data": {
    "incident_id": "inc_776",
    "service": "checkout-api",
    "action_taken": "pod-restart",
    "confidence": 0.98
  }
}

Security Verification

Do not trust requests without a signature. All CartNerve webhooks include a `X-CN-Signature` header calculated using HMAC-SHA256 with your webhook secret.

Verified Signature Required