Hosting type Change
When registering a WABA with 360dialog, there are 2 different hosting options: On-premise API (hosted by 360dialog) and Cloud API (hosted by Meta).
When using Cloud API, a Webhook should be set per WABA, and not per Phone number. This means that traffic from all Cloud numbers in the same WABA will go through the same Webhook. See how to Set Webhook URL per WABA.
When changing hosting type from On-premise to Cloud, the Webhook previously set for the Phone number will be used for the whole Cloud WABA. If you change the hosting type of a second number from On-premise to Cloud, the webhook will not change.
To migrate a WABA from a 360dialog On-Premise to Cloud API, please refer to our instructions below:
Before migrating a number, it's important to go ensure the following:
- 1.The number is conected and registered under a On-premise hostingConfirm that the WhatsApp Business API account is connected and registered under On-premise hosting type.
- 2.Access to 360dialog HubThe process is handled in the 360dialog Hub. You must either be a Direct Client with 360dialog or have a Partner with Cloud API enabled.
In the 360dialog Client Hub > Details page for any number, there is a property Hosting Platform Type.
.png?alt=media&token=e02362f0-06a5-49c7-8dc7-b57a0589e875)
From there, you can launch the Cloud migration assistant.
.png?alt=media&token=d64d3d7d-f3e3-4f30-bfb9-cf7a496692b8)
Your request will be processed. You either wait for it to be done or close the pop-up. You will receive a notification in your Notification Center whenever the migration is completed.
.png?alt=media&token=644f059e-ca50-49eb-a3ba-2b0aa6f80c85)
Done!
.png?alt=media&token=33104d26-2bd0-46fd-83ff-56ac03339c8c)
After the number is migrated, the Hosting Platform Type will appear as below:
Hosting Platftom Type after Cloud API migration
The migration time process per WABA takes ~3 min.
After the migration:
- Make sure you are calling the correct endpoint:
https://waba-v2.360dialog.io/messages - Make sure you are using the most recently generated API KEY. Old API KEYs will not work on the Cloud API. It is highly recommended that you generate another API key after the migration. See Cloud API Authorization Errors for more information.
- Use the WABA Webhook endpoint to configure a new Webhook for all Cloud numbers in this WABA. If you don't do so, the Webhook previously set for the On-premise phone number will be used.