How to add WhatsApp to your SaaS with Embedded Signup and Coexistence
A SaaS adds WhatsApp by connecting each customer's existing number through Meta's Embedded Signup with Coexistence, so the number keeps working in the WhatsApp Business app. With easyCoexistence's Partner API, one connect session per customer runs that flow on a hosted page, Meta delivers the number's messages to your webhook_url, and your backend replies through the Cloud API with the customer's own token.
Fixed throughput of a number used with both the WhatsApp Business app and the Cloud API.
The oldest WhatsApp Business app version a customer's number can connect with through Coexistence.
How far back the chat history Meta can share at onboarding goes; it has to be synced within 24 hours.
WhatsApp's customer service window after a user's message or call; each new message resets it.
The date Meta deprecated Embedded Signup v2 and v3, with integrations moved to v4.
What are the parts of a WhatsApp integration?
Five, and easyCoexistence takes on the first and the last. Your product keeps the conversation logic, the inbox and whatever your model or your customers' staff write, while Meta carries the messages between the number and your server:
What does Coexistence change for your customers?
They keep their number and their phone. The WhatsApp Business app goes on working beside the Cloud API, so staff answer on the phone while your product answers through the API, and what they send from the app reaches your webhook as smb_message_echoes. Three limits come with it: the number sends at a fixed 20 messages per second, only the API can send templates, and Meta disconnects the number when the phone stays inactive for about 14 days.
How does the connect step look in your product?
A Connect WhatsApp button that calls POST /connect-sessions from your backend with a redirect_url, your customer's id as external_ref, and webhook_url with webhook_verify_token, so Meta routes the number to you from its first minute. The customer confirms a short checklist on the hosted page, runs Meta's popup, scans a QR code with the WhatsApp Business app and returns to you with a connection_id. Whether to run Embedded Signup from your own Tech Provider app instead is weighed in the Embedded Signup guide.
How do messages reach your backend?
From Meta, straight to the webhook_url, with no stop at easyCoexistence and no copy kept. The messages field carries what customers send and the status of what you send, and smb_message_echoes carries what staff send from the app. Meta signs each delivery with easyCoexistence's app secret, which is never shared, so a long random secret in the URL path authenticates it. Two numbers in one WhatsApp Business Account share a destination: route on value.metadata.phone_number_id.
How does your backend reply and send templates?
With Meta's Graph API and the customer's token from GET /connections/{id}?credentials=1, which also returns the send_endpoint. Free-form text goes out within 24 hours of the person's last message; after that, only a template Meta has approved:
- Reply: POST /<
PHONE_NUMBER_ID>/messages with type text, inside the window. - Template: the same call with type template, a template name and its language code.
- Create a template: POST /<
WABA_ID>/message_templates, then poll its status, since review results do not reach yourwebhook_url. - Media: POST /<
PHONE_NUMBER_ID>/media to upload; incoming media arrives as an ID to fetch with the same token.
curl -X POST "$SEND_ENDPOINT" \
-H "Authorization: Bearer $CUSTOMER_TOKEN" \
-H "Content-Type: application/json" \
-d '{
"messaging_product": "whatsapp",
"to": "5511987654321",
"type": "text",
"text": { "body": "Your table for 4 is booked for 8 pm." }
}'Can your product import the customer's existing chats?
Once, at connection. With a webhook_url set on the session, easyCoexistence asks Meta to send the number's contacts and, if the customer agrees in the app, up to 180 days of chats, which arrive as smb_app_state_sync and history webhooks. Meta allows it only within 24 hours of connecting, so have the endpoint answering before the link goes out. The chat history guide covers the payloads.
Who pays Meta for the messages?
Your customer. Meta bills the messages your backend sends through the API to the customer's own WhatsApp Business Account, on a payment method they add there, and a business with none cannot send marketing templates. easyCoexistence charges your account per connected number and never charges for messages or marks up Meta's prices.
What happens when a number drops?
Your events URL receives connection.disconnected with Meta's reason when it is known. PRIMARY_INACTIVITY is the 14-day rule, and a new connect session for that customer brings the same number back. connection.token_missing means the number connected without the customer's token, so it receives messages but cannot send until a new session reconnects it.
Common mistakes
- Sending the connect link before your webhook endpoint answers. The history import runs once, within 24 hours of connecting, and content sent before your URL works is lost.
- Answering with free text after the window closes. Once 24 hours pass since the person's last message, only an approved template goes through.
- Firing a campaign from one number at full speed. A Coexistence number sends at 20 messages per second, so queue each number's sends at that rate.
- Expecting staff to send templates from the phone. In Coexistence only the API sends them, so put template sends in your product.
easyCoexistence adds WhatsApp to your SaaS with Meta's Embedded Signup and Coexistence on a hosted page that shows your name: your customers keep their number and the WhatsApp Business app, Meta delivers messages to your server and drops reach you as signed events. The same API connects Instagram, Facebook, TikTok, YouTube, LinkedIn and more channels. US$ 9 to US$ 0.75 per connection per month, falling as you add connections, with the first 3 days free.
easyCoexistence is a multichannel API and MCP server that connects AI agents such as Claude and ChatGPT to WhatsApp, Instagram, TikTok, Facebook and more. On WhatsApp it uses Coexistence: the business keeps using its number in the WhatsApp Business app while the AI works through Meta's official API.
Frequently asked questions
Can a customer connect a number that is on another WhatsApp API provider?
Not while it is there. The hosted checklist asks for a number with no other API provider or automation tool on it, so the customer disconnects it from that provider first.
Can my SaaS send WhatsApp templates for its customers?
Yes, through the Cloud API with each customer's token: create the template on their WhatsApp Business Account, wait for Meta's review, then send it.
Does easyCoexistence read my customers' WhatsApp messages?
No. Meta delivers a number's messages straight to the webhook_url you set. A number with no webhook_url falls back to easyCoexistence's callback, where messages are dropped without being stored.
How much does easyCoexistence cost per WhatsApp number?
US$ 9 to US$ 0.75 per number per month, by the band of your total connections, with the first 3 days free. Meta's message charges go to each customer's own WhatsApp Business Account.
Keep reading
Connect your first channel in two minutes.
No platform reviews to wait for. Connect WhatsApp, Instagram, TikTok or another channel, then ask your AI to post, reply or report, and watch it work.
- 3 days free
- Cancel any time
- Official APIs only
- Monitored 24/7
Verified on