call.supervision.ringing

Summary

call.supervision.ringing fires when Sautikit starts ringing the supervisor you named in a supervision request. It fires for every supervisor type: a @sautikit/webrtc identity, a SIP device or a phone number. Nothing is billed while the supervisor rings. The next event is call.supervision.started when they answer, call.supervision.ended with reason: "no_answer" when they do not, or call.supervision.failed when the leg cannot be placed.

This event is subscribable as a workspace webhook: add call.supervision.ringing to the events of a subscription created with Create a webhook. Supervision events are subscribed by name; there is no call.supervision.* wildcard. Delivery is at least once, so deduplicate on the X-Sautikit-Event-Id header.

Payload

The body is flat. The event kind travels in the X-Sautikit-Event-Kind header.

{
  "workspace_id": "01900000-0000-7000-8000-000000000002",
  "call_id": "9d2b1f53-8c0e-4f1d-9a6b-5d3a8c47e9f0",
  "session_id": "HD_24d73b4518bc",
  "supervision_id": "0f6d3c1e-5a8b-4c2d-9e7f-1a2b3c4d5e6f",
  "mode": "listen",
  "supervisor": {
    "type": "client",
    "identity": "mary",
    "label": "Mary Wanjiku"
  },
  "occurred_at": "2026-09-30T09:15:04Z"
}

Every supervision event carries workspace_id, call_id (the supervised call's UUID), session_id (its HD_ session id), supervision_id, mode, supervisor (type, then identity for client and sip or number for phone, and label when you set one) and occurred_at.

Headers

Next steps

• Supervise live calls: start, switch and stop supervision.
• Webhook concepts: delivery, retries and subscriptions.