bridge and transfer calls using Bandwidth Voice API BXML verbs
domain: bandwidth.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Return a Bridge BXML verb with a target call ID to join two active calls together.
Handle the Bridge Complete or Bridge Target Complete webhook to determine which leg hung up first and clean up state accordingly.
Alternatively, return a Transfer verb with up to 8 destination phone numbers to move a party onto a new outbound call.
Supply a transferAnswerUrl to run additional BXML (e.g., a whisper/announcement) when the transfer target answers, before the calls are bridged.
Use transfer completion webhooks to detect failure (busy/no-answer/rejected) across multiple destination numbers and handle fallback.
Known gotchas
Bridge and Transfer have different completion semantics — Bridge fires one of two different 'who hung up first' webhooks, while Transfer's callback flow hinges on whether transferAnswerUrl was supplied; conflating the two leads to missed cleanup logic.
Transfer supports a maximum of 8 destination numbers per request — call lists larger than that need to be split or sequenced by your own application logic.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?