WhatsApp Cloud API or Coexistence: which one a number needs
Coexistence is not an alternative to the Cloud API, it is a way of onboarding onto it. A plain Cloud API number belongs entirely to software. A Coexistence number runs the API and the WhatsApp Business app at once, so a team can keep answering from the phone.
- Same API underneath, different onboarding
- Coexistence keeps the app, plain Cloud API does not
- The choice is about who answers, not about features
Nothing charged for 7 days. Cancel anytime.
Free text window after a customer message. Identical on both.
Group chats available through the API on a Coexistence number, on any provider.
Sharing chat history is chosen once during onboarding and cannot be changed later.
Are the Cloud API and Coexistence actually different things?
No, and the framing trips people up. The Cloud API is Meta's hosted WhatsApp Business Platform. Coexistence is a mode of onboarding a number onto that same API, one that leaves the WhatsApp Business app working on the number afterwards.
So the endpoints are the same, the message format is the same, templates work the same way and the 24 hour window applies identically. Anything written against one works against the other.
What differs is what happens to the phone. Onboard a number the ordinary way and the Business app stops working on it: the number now belongs to software, and whoever was answering has to answer through whatever was built. Onboard through Coexistence and both surfaces are live, each seeing what the other sends.
| Coexistence | Plain Cloud API | |
|---|---|---|
| The WhatsApp Business app | Keeps working on the number | Stops working on it |
| Who can answer | The team, software, or both | Only through software |
| Existing chat history | Optionally synced at onboarding | Not applicable |
| Group chats via API | Not available | Not available |
| Sending throughput | Fixed by Meta | Scales with quality and tier |
| Suits | A number a team still lives in | A number only software touches |
When is plain Cloud API the better choice?
When nobody needs to answer by hand on that number, which is more common than it sounds.
A notifications number that only sends order updates has no human side to preserve. A brand new number bought specifically for an integration was never in anyone's app. A high volume support line already running through a helpdesk has its human workflow somewhere else entirely, and putting the WhatsApp Business app back in the middle would fragment it.
In those cases Coexistence adds a constraint for nothing: throughput on a Coexistence number is fixed by Meta rather than scaling with quality and messaging tier, and the periodic device activity requirement is a maintenance obligation you would be taking on with no benefit.
When is Coexistence the only option that works?
When the number already carries a business and a person is already answering on it.
That covers most small companies, and effectively every number an agency inherits. The number is printed on a vehicle, a storefront, invoices and a website. Someone answers it from a phone during the day and knows every regular customer by name. Telling that person the app will stop working is the end of the conversation, and it is why so many businesses ended up on unofficial gateways instead of the official API.
Coexistence is what removed that trade. The app keeps working, the team learns nothing new, and software gets the same API it would have got anyway.
Can a number move between the two later?
A number can be disconnected and reconnected, so the decision is not permanent in the way people fear. What is permanent is the chat history choice.
When a number first connects through Coexistence, Meta asks whether to share existing conversations with the API. That is a one time onboarding decision and cannot be revisited afterwards. If you decline and later want the context, the only route is disconnecting and connecting again.
So the choice worth being careful about is not which mode to onboard in. It is whether to say yes to history on the day, because that is the one that does not come back around.
Common mistakes
- Treating Coexistence as a lesser API. It is the same Cloud API, reached through a different onboarding, with the same endpoints and the same rules.
- Choosing Coexistence for a number nobody answers by hand. It adds a device activity obligation and a fixed throughput ceiling in exchange for a phone workflow that does not exist.
- Declining chat history at onboarding and expecting to add it later. That choice is made once and cannot be changed.
EasyCoexistence onboards a number through Coexistence and then watches the connection. US$ 9 per number per month, first 7 days free. Meta bills its own messaging costs directly to you.
Frequently asked questions
Is Coexistence slower than the plain Cloud API?
Throughput on a Coexistence number is fixed by Meta rather than scaling with quality rating and messaging tier. For conversational use that ceiling is rarely the constraint, but for high volume sending it can be.
Do templates work the same way on both?
Yes. Templates are submitted to Meta for review and sent through the API identically. On a Coexistence number the phone app cannot send them, so anything outside the 24 hour window has to go through the API.
Can I put a brand new number on Coexistence?
It has to be registered in the WhatsApp Business app first, since Coexistence connects a number the app is already using. For a number nobody will answer by hand, ordinary Cloud API onboarding is the better fit.
Which one do agencies use for client numbers?
Coexistence, almost always. A client's number is one their staff already answers, and migrating it would take the WhatsApp Business app away from them, which no client agrees to.
Keep reading
Ready to get started?
Set up WhatsApp Coexistence in minutes, not months. The app keeps working on the phone.
Start Free TrialNothing charged for 7 days. Cancel anytime.Verified on