​

WhatsApp Cloud API

​

At A Glance

​

Minimal Config

[whatsapp]
enabled = true
webhook_bind = "127.0.0.1:8080"
webhook_path = "/whatsapp/webhook"
access_token_env = "WHATSAPP_ACCESS_TOKEN"
phone_number_id_env = "WHATSAPP_PHONE_NUMBER_ID"
verify_token_env = "WHATSAPP_VERIFY_TOKEN"
app_secret_env = "WHATSAPP_APP_SECRET"

​

Smoke Test

loong channels send whatsapp --target "+15551234567" --text "hello from loong"
loong channels serve whatsapp

​

Command Surface

​

Required Fields For Send

​

Required Fields For Serve

​

Gateway And Ownership

​

Operator Notes

• This page documents the current WhatsApp Cloud API business-account lane: outbound sends are shipped and the webhook reply service is also implemented.
• Serve mode needs verify_token and app_secret in addition to the Cloud API access token and phone number id.
• Keep the Cloud API credential path distinct from the QR-linked WhatsApp Personal surface so operators do not confuse Meta business credentials with personal-account pairing.

​

Related Docs

• Continue to WhatsApp Personal for the QR-linked personal-account bridge lane.
• Continue to Channel Guides for the full shipped channel matrix.
• Continue to Channels for the conceptual surface model.
• Continue to Channel Setup for the shared public setup contract.
• Continue to Gateway And Supervision when this surface needs longer-lived runtime ownership.