Blind transfer or forward a call to another destination
/org/{tenant_code}/v2/calls/{uid}/transfer
Platform support: MT and CC
Blind (unattended) transfer of the live call identified by uid: the party connected to
this leg is sent to destination and the leg itself is released. There is no consultation
step — the transfer completes whether or not the destination answers.
If uid is still ringing in (not yet answered), this redirects the calling party before
answer — i.e. call forwarding — rather than transferring an established call.
202 Accepted means the transfer was requested on the PBX, not that it has completed.
Watch the event_call_* event stream, or re-read the call, to observe the outcome.
Scope rules match the other single-call endpoints: a user token may only transfer its own extension's call; an API key / service may transfer any call in the tenant.
Request
Responses
- 202
- 400
- 401
- 404
- 422
- 500
- 504
Transfer accepted
Missing, empty, or malformed transfer destination
Missing or malformed user identity
The requested resource or scope is not available. Returned, for example, when the system scope is used on a non-multi-tenant deployment, or with a non-API-key identity.
The call cannot be transferred from its current state — an outbound call that is still ringing, a call with no established state, or a dialer agent call that has not yet connected to the lead.
Internal server error
The proxy timed out waiting for the processing thread to service the request. For call initiation the call may still proceed on the PBX; for a list request no state is changed. The timeout only bounds how long the request is held open.