Webhooks

Security-event subscriptions and delivery diagnostics.

Security-event subscriptions and delivery diagnostics.

This screen belongs to the Secure 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. Webhooks → Add webhook → name and approved URL.
  2. Choose events, optional HMAC secret, enable and Create.
  3. Open the card → Ping → Deliveries.
  4. Check receiver event ID, signature and HTTP result.
  5. Pause with Edit → disable Enabled → Save; coordinate secret changes with the receiver.

Every control and its meaning

Control / parameterValues, units and effect
Название, URLReceiver URL must use http/https and be reachable from the gateway; name describes the subscription.
События / EventsSelect a nonempty set; alert.rule.triggered is for alert rules. Use events exposed by your version.
Секрет HMACOptional signing secret; empty during edit preserves it. The receiver validates signatures.
Активен / EnabledEnables subscription delivery, not detection. Delivery, Ping, Replay and secret rotation are separate actions.

Verify the result

A saved URL does not prove delivery: obtain an attempt record and receiver event. Replay can repeat an external effect.

Errors, disabling and reverting changes

For timeouts/4xx, check network/endpoint/signature while retaining the subscription. The old secret cannot be retrieved after rotation; coordinate the new one.

Webhook form with a synthetic receiver · actual staging
Webhook form with a synthetic receiver · actual staging
2026-10-15 · Actual staging application and an existing operator session. Synthetic data or non-personal configuration only; credentials and the operator profile are excluded. A form alone does not establish persistence or replica consistency.
  1. URL
  2. Events
  3. Create

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