Call Status (BSUID)

🚧
BSUID-First Contract: This is the BSUID-first version of the webhook. bsuid is always present and is the primary identifier. waId (phone number) is optional and may be omitted. Consumers must identify the user by bsuid, not phone.

{
  "eventType": "call.status_bsuid",
  "call_id": "call_wati_987654321",
  "metadata": {
    "direction": "inbound",
    "status": "completed",
    "from_number": "+12025550101",
    "to_number": "+12025550199",
    "duration_seconds": 332,
    "timestamp": "2026-02-23T10:15:45Z",
    "operator_id": "operator_sarah_01",
    "team_name": "Customer Support"
  },
  "bsuid": "HK.xxxxxxxxxxxxx",
  "parentBsuid": "HK.ENT.xxxxxxxxxxxxx",
  "username": "@bob"
}

Field Descriptions

Field Name	Type	Description
eventType	string	Event type: "call.status_bsuid" — BSUID-first version
bsuid	string	Required. Business Solution User ID — the primary stable cross-channel identifier. Always present in this webhook version.
parentBsuid	string	Required. Parent BSUID — the enterprise-level identifier.
username	string/null	Human-readable username handle for the contact.
waId	string/null	WhatsApp ID / phone number of the contact. Optional — may be omitted in BSUID-first mode.

📘
For full field reference, see the Call Status webhook documentation.

BSUID-First Contract: This is the BSUID-first version of the webhook. bsuid is always present and is the primary identifier. waId (phone number) is optional and may be omitted. Consumers must identify the user by bsuid, not phone.

Field Descriptions

For full field reference, see the Call Status webhook documentation.

BSUID-First Contract: This is the BSUID-first version of the webhook. `bsuid` is always present and is the primary identifier. `waId` (phone number) is optional and may be omitted. Consumers must identify the user by `bsuid`, not phone.