@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:
- Request to enable WhatsApp Connector (Accept + Initiate) for project
- Whatsapp call is not enabled for this project
- 403 "whatsapp call is not enabled for this project"
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:
- Native WhatsApp Calls integration with SIP, Native WhatsApp Calls integration with SIP
- WhatsApp Calling SIP inbound from LiveKit not ringing (drops during dialing), inbound flow with troubleshooting