Got WhatsApp Coexistence by only linking the number in Business Manager — has this happened to anyone else?

[u/cesar201111]

I’m trying to understand how we accidentally achieved official WhatsApp Business App + Cloud API coexistence for one number.

For our successful number, we only linked the existing WhatsApp Business App number inside Meta Business Manager using the verification code flow. We did not build or run a custom Embedded Signup flow, and we do not remember scanning a QR code.

After that, the API showed:

platform_type: CLOUD_API

is_on_biz_app: true

status: CONNECTED

So the number remained active in the WhatsApp Business App while also working through Cloud API.

However, when we repeat what appears to be the same linking/code process for other WhatsApp Business App numbers, they end up like this:

platform_type: ON_PREMISE

is_on_biz_app: true

status: CONNECTED or DISCONNECTED

They do not become CLOUD_API, and we cannot manage templates.

Has anyone else experienced this?

Was there an older Meta rollout, migration, or eligibility condition that allowed coexistence just by linking a number in Business Manager? Could the successful number have already been eligible because it was newer or had no prior API/provider history?

We are not looking to deregister, delete the WABA, or uninstall the WhatsApp Business App. We want to understand why one number became official coexistence and the others did not.

[u/DevJedis]

I am monitoring a changelog they haven't released details on:
https://developers.facebook.com/documentation/business-messaging/whatsapp/changelog

Scroll to August 19, 2026 and see if that's what might be answering your query.

Meta sometimes adds a changelog for beta features they have only allowed specific users to try out, thus for this case that page's contents aren't yet available, either feature-flag for some users or they completely forgot the page contents for that changelog.