Skip to content

Webhook notifications

Get alerts where your team already works. Webhook notifications push real-time alert events from Blecon Track straight to Slack, PagerDuty, your own dashboards, or any system that accepts HTTP — so the right people know the moment something needs attention, without watching a screen.

How it works

When an alert rule creates or resolves a violation, the system sends an HTTP POST to your configured webhook URL with details about the event: which rule triggered, which device or location is involved, the severity, and a timestamp.

Notifications are sent for both new violations and resolved violations, so your systems can track the full lifecycle of each alert.

Setting up webhooks

  1. Go to Settings > Webhooks in Blecon Track.
  2. Click Add Webhook and enter your endpoint URL.
  3. When creating or editing alert rules, select which webhook channels should receive notifications.

What's in a notification

Each webhook notification is delivered as a JSON array containing a CloudEvents object. The payload includes:

  • Alert rule — The rule name, type, and severity.
  • Device or location — The device ID (or zone ID for zone asset count rules).
  • Notification type — "new" when a violation is created or "resolved" when it clears.
  • Violation status — Current violation state.
  • Timestamp — When the event occurred.

Signature verification

Each webhook POST includes an X-Tracker-Signature header containing an HMAC-SHA256 signature of the request body. Use this to verify that notifications came from Blecon and were not tampered with.

The header format is:

X-Tracker-Signature: sha256=<hex_digest>

Track webhooks vs Network webhooks

Blecon Track webhooks deliver alert notifications — rule triggers and violation events.

Blecon Network webhooks deliver raw data events — position updates, device connections, and sensor readings.

They serve different purposes and are configured in different places.

Questions? Contact Blecon support — we're happy to help.