Webhook Event Object

The canonical webhook event object contains id, type, created_at, sequence, and data.

{
  "id": "evt_20260901T173552.838849267_47feba5c0ce326f4",
  "type": "call.completed",
  "created_at": "2026-09-01T17:35:52.838Z",
  "sequence": 2,
  "data": {
    "call": {
      "id": "call_20260901T173513.576013050",
      "application_id": "app_20260321T130033.289233019",
      "direction": "outbound",
      "from": "+37045509630",
      "to": "+37067613663",
      "status": "completed",
      "carrier_call_id": "eb3ca595-8c80-4590-8997-310682ce0a5f"
    },
    "reason": "completed",
    "duration_seconds": 12,
    "billable_seconds": 5,
    "hangup": {
      "cause": "NORMAL_CLEARING",
      "source": "unknown",
      "sip_code": 200
    }
  }
}

Field	Required for new events	Description
id	Yes	Stable logical event ID and deduplication key.
type	Yes	Webhook event type.
created_at	Yes	UTC RFC 3339 timestamp with millisecond precision.
sequence	Yes	Per-call generation sequence. Historical events can lack it.
data.call	Yes	Common call snapshot. Optional call fields can be omitted.
data.metadata	No	Supported customer-supplied call metadata.

See Event Structure and Reference for event-specific objects and examples, Headers and Signatures for request authentication, and Retries and Idempotency for delivery semantics.