About This Event
Thetransfer_started webhook is triggered when Altur records that a call transfer handoff has started. Use it to prepare real-time context for the human agent who may receive the transferred call.
Event Details
- Trigger: Automatically triggered when the transfer handoff starts.
- Purpose: To notify your backend or CRM before the human transfer leg connects.
Request Details
- HTTP Method:
POST - Content Type:
application/json - Endpoint: The URL you configure in your webhook integration settings.
- Authentication: Includes the
X-Altur-Signatureheader for HMAC verification.
Payload Example
Transfer Fields
All other fields match the
on_call_end call payload.
The payload describes the call at the moment of the transfer:
status is
in-progress, answered_by is human, and ended_at, ended_by, ended_reason, duration and
billed_duration are null. The transcript contains the messages Altur has
received up to the transfer; the last few lines spoken right before the
transfer may occasionally be missing. Use on_call_end for the full
transcript. The end_user and campaign_user objects reflect their values
when the event is sent.status and answered_by filters, evaluated against the call state at the moment of the transfer (status: in-progress, answered_by: human), not the final call state. For example, a filter of status: ["ended"] blocks every transfer webhook for that integration.
Timestamps use the same format as on_call_end: ISO 8601 with a +00:00 offset and optional fractional seconds (e.g. 2026-09-30T21:08:12.340917+00:00).