Whatsapp calls inbound

Client SDKs
1

We successfully receive WhatsApp inbound call webhooks from Meta and can hit the call accept API, but we’re blocked on generating valid SDP answers. Python SDK only exposes SIP APIs and Node SDK lacks WhatsApp call wrappers. Is there a supported WhatsApp media bridge or beta API for this?

2

@Samiksha, the path you’re on (Meta Cloud API webhook >> generate SDP answer >> bridge to LiveKit) isn’t the supported integration today. LiveKit doesn’t ship a WhatsApp Cloud API media-bridge SDK in Python or Node, which is why the wrappers aren’t there.

Supported path is SIP-based via Meta’s WhatsApp Calling SIP endpoint (wa.meta.vc):

Enable WhatsApp Connector on your LiveKit Cloud project: it’s a per-project allowlist gate controlled by the LiveKit team. Most recent enablement ask with the right pattern: Request: Enable WhatsApp Connector for LiveKit Cloud project. Same gate tracked in:

Opus required: WhatsApp Calling needs Opus, not G.711. Tracked in Support Opus on SIP Trunks · Issue #281 · livekit/sip · GitHub (open).

ALPN: Meta’s TLS endpoint needs ALPN “sip”. Was hardcoded; fixed in TLS handshake: Outbound TLS calls fail with Meta (wa.meta.vc) due to hardcoded ALPN "sip" · Issue #685 · livekit/sip · GitHub.

Once the connector is enabled, you create a standard LK SIP inbound trunk pointing at the WhatsApp endpoint. Meta routes the call into LiveKit via SIP; no SDP plumbing in your backend.

@CWilson @darryncampbell can confirm the enablement process. Reference threads worth skimming while you wait:

3

The documentation for the WhatsApp connector should be available very soon and we’ll no longer require users to register to enable the feature. Please look out for announcements in this community