Webhooks

Event subscriptions and signed-delivery diagnostics.

Event subscriptions and signed-delivery diagnostics.

This screen belongs to the Router deployment operator, not an ordinary hosted customer. Hosted customers have a separate account page with their own keys and limits; policy and service settings are not exposed there. Contact the operator to change protection. In the operator console, open the route listed above; a report tenant filter does not automatically scope a global setting.

Examples use educational data. Use your own authorized tenant in real integrations. Each screenshot shows the actual frontend, with the source and educational/demo mode stated below it.

Step-by-step actions

  1. Open Webhooks → Create webhook.
  2. Enter a name and an approved test receiver endpoint.
  3. Choose events and configure the secret; enable receiver signature checks.
  4. Enable the subscription, create it and reread its card.
  5. Use Ping/Test and Delivery history; verify the HTTP response and the received event.
  6. To pause it, edit the subscription, disable Enabled and save.

Every control and its meaning

Control / parameterValues, units and effect
Имя, URLName is required; an http:// or https:// URL points to the receiving endpoint, not the service’s web page.
События / EventsChoose at least one listed event. Select alert.rule.triggered for alert rules and other events as needed.
Секрет / SecretHMAC-SHA256 supports receiver signature validation. Empty during editing preserves the existing secret; never publish it.
Активен / EnabledControls this subscription’s delivery. Disabling it does not stop classification, quotas or audit capture.

Verify the result

A successful HTTP response plus the matching receiver event ID confirms delivery. A saved subscription alone does not.

Errors, disabling and reverting changes

For timeouts/4xx, fix the endpoint and signature checks. Replay repeats an external effect, so use idempotency. Coordinate secret rotation with the receiver.

Webhook form · actual staging
Webhook form · actual staging
2026-10-15 · Actual staging application. Synthetic client, public definitions or aggregate test-stand metrics only; not customer statistics or a benchmark. Original pixels are unmodified; personal profile and private data excluded. example.invalid is a placeholder URL. Form unsaved, HMAC empty, no delivery attempted.
  1. Receiver URL
  2. HMAC secret
  3. Select events
  4. Create

Detailed security settings · Traffic analysis · FAQ · All application sections