data, with channel: "voice" and timestamp at the root level.
Fields that do not apply to an event come as null.
Lifecycle events
data fields
Call identifier (the
bulkId returned when triggering, or the callId
returned by POST /voice/live/start for stream calls). Lets you correlate
all events of the same call/batch.Identifier of the individual call within the batch, or
null (always null
for stream calls).true when the call was answered. In call.answered it is always true. In
call.ended it can be true, false or null. In other events, null.Talk time in seconds. Present in
call.ended (may be null); null in other
events.Key pressed in
call.dtmf — a single character: "0"–"9", "*" or "#".
null in other events.Numeric hangup code (Q.850 + custom codes). Present in
call.ended (may be
null); null in other events. See the cause table.Description in pt-BR matching the
cause, or null. For a code without a
mapped description, it returns Causa <n>.Examples by event
call.started — call started
call.started — call started
The other fields come as
null.call.answered — call answered
call.answered — call answered
answered is always true.call.dtmf — key pressed (one webhook per key)
call.dtmf — key pressed (one webhook per key)
digits carries one key. Each key pressed generates a separate
webhook.call.ended — call ended
call.ended — call ended
Includes
talkSeconds, cause and causeDescription.cause table
The cause field follows the Q.850 codes plus two custom codes (150 and
151). causeDescription carries the matching description in pt-BR — the
values below are returned exactly as shown.
For a
cause without a mapped description in the table, causeDescription
returns the generic text Causa <n>.