WhatsApp Cloud API
Connect a business phone through Manual Cloud API and check inbound messages, replies and templates separately.
What you need
Prepare an authorized Meta developer/business account, a WhatsApp Business Account and the intended business phone number. Start with Meta’s permitted test assets and a test recipient. Use a token with the access required for the actual operation. Meta identifies whatsapp_business_messaging for messaging and whatsapp_business_management for account/template management; business_management is needed only for applicable business-portfolio operations.
Create and prepare the Meta app
1. Collect the correct Meta values
Open Your Meta app → WhatsApp → API Setup / Getting Started
Business/app owner
- Use the Meta app that will operate the intended WhatsApp business assets. Open its WhatsApp setup area. Complete the business/account prerequisites shown there.
- Start with the test number/recipient flow offered by Meta. Find Phone Number ID for the selected sending number. Copy the ID, not the visible telephone number.
- Find WhatsApp Business Account ID for the same assets. Keep it separate from the business portfolio ID and Phone Number ID.
- Obtain the supported test Access Token with access to those assets. Note its expiry and store it privately. An App Secret is not the access token.
- Before continued operation, prepare the appropriate supported business/system-user token and asset assignments. Do not assume a temporary setup token is permanent.
Expected result The token, Phone Number ID and WABA ID refer to the same intended business/number.
If this does not happen If the number or account differs between screens, stop and select the correct asset before connecting it.
| Wizard field | Where the value comes from | Do not confuse it with |
|---|---|---|
| WhatsApp Cloud API Access Token | The authorized token from the app/business setup. | App Secret, verification token or a telephone number. |
| Phone Number ID | The selected WhatsApp sending number’s API identifier. | The displayed phone number, WABA ID or portfolio ID. |
| WhatsApp Business Account ID | The WABA containing the number/templates. | Business portfolio ID. |
| Webhook Verify Token | A private value you set for this channel’s callback verification. | WhatsApp access token. |
| Callback URL | Read it from this application’s wizard. | OAuth callback or a callback copied from another installation. |
Connect it in MarkHub or Waziper
2. Enter the token and number
Open MarkHub / Waziper workspace → Channels → WhatsApp setup
Workspace user authorized to connect the business number
- Open
/portal/channels/connect/whatsapp/setup?method=cloud_apion your own application domain, or use the available WhatsApp connection in Channels. - Choose Manual Cloud API if the method is not already selected. The source also labels its selection action Use Business API; once chosen, it can show Selected.
- Enter WhatsApp Cloud API Access Token privately. Select Save & Continue.
- Enter Phone Number ID. Enter WhatsApp Business Account ID for the matching WABA, especially when using its templates/account operations.
- Check the number/account details and select Save & Continue to reach the webhook step.
Expected result You reach the step showing Webhook Verify Token and the application’s Callback URL.
If this does not happen If a field fails validation, correct that field. Do not put the visible phone number in Phone Number ID or create a second channel to bypass the error.
3. Verify the webhook and save the channel
Open Application wizard + Meta WhatsApp webhook settings
Workspace user and authorized Meta app owner
- In the application wizard, set Webhook Verify Token. Copy the exact Callback URL shown for this channel. Keep the wizard open.
- In the Meta app’s WhatsApp webhook configuration, enter that URL in Callback URL and the identical private verification value in Verify token.
- Use Meta’s verification/save action. After verification succeeds, subscribe the intended WABA/number to the message events required by the integration.
- Return to the wizard and complete its available verification checks. Select Save channel when the final step offers it.
- Open Channels and confirm the saved number belongs to the intended workspace. Complete the inbound/reply test below before treating setup as finished.
Expected result The provider verifies the callback and the application saves the intended business channel.
If this does not happen For a verification error, compare the two token values, the full public HTTPS URL and the selected app. For no inbound events, check the event subscription and Phone Number ID.
Test messages and templates
4. Check an inbound conversation and reply
Open Permitted test recipient + the application’s Inbox
Workspace user
- From the permitted test recipient, send a fresh test message to the connected business number.
- Open the intended workspace’s inbox. Select the conversation with that sender and confirm the inbound text.
- Reply promptly from that conversation using content intended for the test recipient.
- At the recipient, confirm the reply arrived. In the application, inspect the available delivery/error state rather than relying only on a send-success notice.
- For a business-initiated template test, select the actual Approved template/language for that WABA and an opted-in permitted test recipient. Check delivery separately.
Expected result An inbound message appears in the correct workspace and the intended recipient receives the reply/template.
If this does not happen If sending is refused, check the actual provider error, recipient eligibility, token access and the applicable conversation/template requirements before retrying.
| Check | Complete only when… |
|---|---|
| Incoming message | The sender’s new message appears once under the correct business channel. |
| Reply | The same test sender actually receives the intended reply. |
| Template | The correct WABA, language and approved template are used and the test recipient receives it. |
| Webhook | Ownership verification works and the actual required events reach the correct channel. |
Which review do you need?
Manual use of your own business assets, onboarding third-party businesses, app permission access, business verification, phone readiness and message-template approval are distinct processes. Select the provider’s process for your actual operating model.
- For an app permission review, demonstrate the actual Manual Cloud API connection and the required messaging/account action. Do not describe an Embedded Signup flow that this edition does not provide.
- Prepare a reviewer test path, permitted test assets and a video showing the result. Use the common 15-step process for submission preparation.
- For a message template, submit the actual name, category, language, variables and sample values using the available template-management process. Check that template’s provider status before using it.
- After approval, test the intended feature again with the approved app/number/template. One approval does not establish all the others.
Common problems
| Problem | What to do |
|---|---|
| Webhook verification fails | Check the full reachable HTTPS callback, verification token and matching workspace channel. |
| Connected but no incoming messages | Check event subscription, the actual Phone Number ID and the number used by the sender. |
| Send accepted but recipient receives nothing | Check provider delivery/error events, recipient eligibility and the applicable message/template rules. |
| Template is not available | Check the WABA, language and template approval status. |
| Connection stops after testing | Check token expiry and asset access before generating another token. |
Fields and version information
These are fields and default paths found in the reviewed source version. An installed module or a source default does not prove platform approval. Copy the complete URL shown by your running installation; do not paste a path by itself into a developer console.
Waziper Official — WhatsApp Cloud API / Channels
| Setting label | Source information |
|---|---|
| WhatsApp Cloud API Access Token | Use the value shown by your installation or issued for your app. |
| Phone Number ID | Use the value shown by your installation or issued for your app. |
| WhatsApp Business Account ID | Use the value shown by your installation or issued for your app. |
| Webhook Verify Token | Use the value shown by your installation or issued for your app. |
| Callback URL | /integrations/channels/webhooks/whatsapp |
Version: 37d44a1727216f5c492205024b323aa522730ebc
Open the source definitionMarkHub — WhatsApp Cloud API / Channels
| Setting label | Source information |
|---|---|
| WhatsApp Cloud API Access Token | Use the value shown by your installation or issued for your app. |
| Phone Number ID | Use the value shown by your installation or issued for your app. |
| WhatsApp Business Account ID | Use the value shown by your installation or issued for your app. |
| Webhook Verify Token | Use the value shown by your installation or issued for your app. |
| Callback URL | /integrations/channels/webhooks/whatsapp |
Version: 68a5655db1bbe17c74fb211f0fe0ee4e63c8be88
Open the source definitionPhone registration, delivery and app/template approval have not been performed by this documentation update.