Receiving Events

call.answeredbeta

This feature is in private beta. Contact technical support to request access for your workspace.

call.answered reports that a managed call connected. Beta workspaces can receive it through subscribed_events containing call.answered or *, or an empty/omitted list.

Event payload

{
  "id": "evt_call_example",
  "type": "call.answered",
  "provider": "whatsapp",
  "account_id": "acc_example",
  "occurred_at": "2026-10-10T12:00:42Z",
  "data": {
    "call": {
      "id": "call_example",
      "direction": "outbound",
      "media_type": "voice",
      "state": "active"
    },
    "sender": {
      "id": "100000000000002@lid",
      "display_name": "Example"
    }
  }
}

Notes

call.answered reports that a managed call connected. Beta workspaces can receive it through subscribed_events containing call.answered or *, or an empty/omitted list.
Call-event access is controlled by workspace is_beta. In beta workspaces, * and empty or omitted subscribed_events include call events; specific lists match only their listed events. Non-beta workspaces may use wildcard subscriptions but never receive call events; explicitly subscribing to call events returns 403 beta_feature_not_enabled. Eligibility is rechecked for every delivery, retry and dead-letter replay; lookup failures do not grant access. Ordinary message.* call records are independent.