What syncs to the API, and what does not
Contacts and one-to-one message history synchronise to the API, and messages mirror both ways from then on. Groups do not, and neither do the WhatsApp Business app's own tools: catalog, orders, status, labels, quick replies, greeting and away messages.
The window after onboarding in which the synchronisation must be started.
Direction of message mirroring once connected: app to API and API to app.
Group chats that synchronise or become reachable through the API.
What crosses over
Two things, and they are the two that matter for software starting on a number a business has used for years.
- Contacts: every contact with a WhatsApp number can be synchronised to the platform.
- One-to-one message history, so the API is not blind to conversations that happened before it existed.
- From then on, messages mirror in both directions: what the API sends appears in the app, and what the team types in the app reaches your systems.
What does not cross over
More than people expect, and this is the list worth reading before promising anything to a client. None of it is a provider limitation; it is how the platform works.
- Group chats, which do not synchronise and are not reachable through the API on any provider.
- Business tools: the catalog, orders and status.
- Messaging tools: greeting message, away message, quick replies and labels.
- Channels, voice and video calls, and the business profile details.
Why the app's own tools stay behind
Because they are features of the app rather than of the platform, and the API has no equivalent of them.\n\nQuick replies and labels live on the device. An away message is something the app sends when nobody is looking at it. None of these exist as API concepts, so there is nothing for them to synchronise into.\n\nThe practical consequence is that a business relying on labels to organise its work keeps using them in the app, and software has no visibility of them. If that organisation matters to what you are building, it has to be rebuilt on your side rather than read across.
The window you can miss
The synchronisation has to be started within 24 hours of onboarding. Miss it and the number has to be offboarded and onboarded again to get another chance.\n\nThis is separate from the 24 hour customer service window that governs sending, and the two get confused constantly. One counts from the customer's last message and decides whether free text delivers. This one counts from onboarding and decides whether history can still be pulled across.\n\nIt is also why history is worth deciding on the day a number connects rather than when the integration work starts, which is usually a different week.
Common mistakes
- Promising a client their labels and quick replies will appear in your system. They stay in the app.
- Building anything around group chats. They do not synchronise on any provider.
- Leaving the history sync until the integration is built. The window is 24 hours from onboarding.
EasyCoexistence runs Meta's onboarding and records each step on the connection timeline, so the day a number connected, and whether history was accepted, is a dated fact rather than something to reconstruct.
Frequently asked questions
Do my old conversations appear in the API?
One-to-one history synchronises if you accept it during onboarding. Group conversations do not.
Can software see my labels?
No. Labels are an app feature with no API equivalent, so they stay on the device.
Does the team lose quick replies?
No. They keep working in the app exactly as before; software simply cannot see them.
What if I miss the 24 hour sync window?
The number has to be disconnected and connected again, which reruns onboarding and opens a fresh window.
Keep reading
Ready to get started?
Set up WhatsApp Coexistence in minutes, not months. The app keeps working on the phone.
Start Free TrialVerified on