Use case: We've built an in-app calling UI for agents handling WhatsApp Business Calling conversations (via the WhatsApp Business Calling API, bridged through Zernio to our own SIP infrastructure). Agents need to be able to end an in-progress WhatsApp call directly from our app's UI — independent of whatever telephony system sits on our forwarding leg. Today the only way a WhatsApp call ends is via the SIP leg tearing down (our side sending BYE) or the consumer hanging up on their end. We have no way to trigger termination from an API call.
What's missing: POST /v1/voice/calls/{id}/end exists for PSTN/voice calls, but it's hard-scoped to the pstn channel — calling it with a WhatsApp call ID returns "Call not found." There's no equivalent for WhatsApp, e.g. POST /v1/whatsapp/calls/{id}/terminate, that would fire Meta's terminate action for a given call ID.
Why maxCallDurationSeconds doesn't cover this: That's a fixed timer cap set on the calling config ahead of time — useful as a safety ceiling, but not an on-demand "end this specific call right now" control. We need the latter.
Ask: An on-demand endpoint to terminate a specific in-progress WhatsApp Business Calling call by its call ID (mirroring the existing PSTN endpoint's shape, e.g. POST /v1/whatsapp/calls/{id}/end or /terminate), that fires the network-level terminate independent of our own SIP/telephony state. A call.ended webhook firing as a result (same as it does today for other end causes) would let us confirm it closed cleanly on our side.
Happy to provide more detail on our setup if useful.
