WhatsApp Business API Setup Checklist: WABA, Templates and Webhooks

The WhatsApp Business Platform gives businesses programmatic messaging, templates, webhooks and team tooling around an eligible WhatsApp phone number. Most setup problems come from missing business access, incomplete phone-number preparation or credentials that belong to the wrong Meta app or business portfolio.

Use this checklist before connecting a number to any platform. For the SocialGeniex connection options, visit the WhatsApp Business API platform page.

1. Confirm business ownership and access

• Identify the Meta Business Portfolio that should own the WhatsApp assets.
• Confirm the person performing setup has the required business and WABA permissions.
• Complete business details and any verification or security actions requested by Meta.
• Review pending invitations and required actions in the Meta dashboards.

Using the correct Facebook account matters. A technically valid login may still return no WABA or phone number if that user cannot access the selected business assets.

2. Prepare the phone number

Decide whether you are onboarding a new number, migrating an existing API number or using a supported coexistence flow. The number must be eligible for the selected onboarding path and able to receive the required verification code.

• Record the display number and its international format.
• Confirm the phone is not locked into an incompatible registration state.
• Complete code verification when requested.
• Keep the two-step verification PIN secure.

3. Record the correct identifiers

Do not confuse the display phone number with Meta object IDs. Operational integrations may require:

• WhatsApp Business Account ID.
• Phone Number ID.
• Business Portfolio ID.
• Meta App ID and Embedded Signup Configuration ID.

Copy identifiers from the authoritative Meta interface and label them before entering them into another system.

4. Use the right access token

The token must belong to the relevant app or system-user setup and include the permissions required for the intended operations. Treat tokens like passwords: never place them in screenshots, public tickets or client-side source code.

For a production integration, plan token ownership and renewal before launch. A temporary token can make an initial test pass and then cause sending to fail later.

5. Configure message templates

Business-initiated communication may require an approved template. Create templates with a clear purpose, correct category and variables that can be populated consistently.

• Use descriptive template names.
• Check language and variable order.
• Avoid misleading placeholders.
• Test media headers and buttons.
• Map approved templates into the sending platform.

6. Wire and test webhooks

Sending is only half of the integration. Webhooks deliver inbound customer messages and message-status events. Confirm the callback is reachable over HTTPS, completes verification and processes events idempotently.

Test at least:

• An inbound text message.
• A media message.
• Sent, delivered, read and failed status updates.
• A customer reply that should open or update a conversation.

7. Run an end-to-end test

1. Send an approved test message to a consented recipient.
2. Confirm the provider returns a message ID.
3. Verify delivery and read statuses update.
4. Reply from the recipient’s WhatsApp account.
5. Confirm the reply appears in the correct team inbox.
6. Check logs for permission, template or webhook errors.

Common setup failures

• Login unavailable: the Meta app may have pending required actions, role restrictions or an unavailable login product.
• No phone number returned: the logged-in user may not have access, or setup is incomplete.
• Template send rejected: the template name, language, variable mapping or recipient window may be incorrect.
• Messages send but replies are missing: webhook subscription or callback routing is incomplete.
• Token works briefly and expires: a temporary token was used without a production token strategy.

Once the channel passes the end-to-end test, connect it to campaigns, automation and team workflows gradually. Create a SocialGeniex account to manage WABA messaging alongside your wider customer operations.