Request: Enable WhatsApp Connector for LiveKit Cloud project

Hi LiveKit team and community,

I’m integrating outbound WhatsApp calls using the Python server SDK (livekit-api) and LiveKitAPI.connector.dial_whatsapp_call with a DialWhatsAppCallRequest.

Could you enable WhatsApp Connector for this project

Details:

  • LiveKit Project URL: wss://videointerview-u00vg3jy.livekit.cloud

  • Project ID : p_10u1x8zlvpr

  • SDK: livekit-api (Python), dial_whatsapp_call

Please let us know if there are additional configuration or onboarding steps required once access is enabled.

Thanks,

Pavan Kumar

@Pavan_Kumar_Varanasi The WhatsApp Connector surface is real and shipped in the Python SDK; from livekit.protocol.connector_whatsapp import * is in livekit-api/livekit/api/__init__.py on main. The bottleneck is Cloud-side enablement on your project.

That’s the WhatsApp Calling beta path CWilson mentioned in thread #691 (WhatsApp Calling SIP inbound from LiveKit not ringing (drops during dialing)). He sends out an onboarding form once you’re added to the beta.

Pinging @CWilson and @darryncampbell to bump this. If it doesn’t move in the forum within a day or two, the faster path is filing a Cloud support ticket directly from the dashboard with the same project ID; that opens an internal ticket against your account rather than waiting on forum cadence.

WhatsApp “connectors” support is currently in Beta. We are working on being able to add enable more folks for the feature.

I learned today that WhatsApp now supports G711. There is a PR in another thread from yesterday that fixes an issues with connecting to WhatsApp.

I am curious why you would use WhatsApp SIP instead of their connector functionality?

Just for anyone else finding this thread, this is true for ship and scale plans, but build plans will not see this option on their cloud dashboard. See more info here: