WhatsApp Business Accounts

What a WABA Is

A WhatsApp Business Account (WABA) is the top-level WhatsApp container inside a Meta Business Portfolio. It groups WhatsApp assets such as:

• Phone numbers
• Message templates
• Webhook subscriptions and messaging-related configuration

In practice, a WABA is the business object your integration targets for setup and management operations.

WABA ID

Each WABA has a unique waba_id. You use this ID for account-level actions, for example:

• App subscription setup (/subscribed_apps)
• Account-level webhook and management operations

WABA vs Phone Number ID

• waba_id identifies the WhatsApp Business Account container.
• phone_number_id identifies a specific sending number inside that WABA.

Both IDs are required in production integrations, but for different API operations.

Ownership Model

WABAs are owned by a Meta Business Portfolio. A business can have multiple WABAs, and each WABA can contain multiple phone numbers, subject to Meta limits and account state.

In Dualhook:

• You keep ownership of your WABAs and numbers in your own Meta assets.
• Dualhook configures coexistence and webhook routing against those assets.
• Dualhook does not become legal owner of your WABA.

Creating a WABA

Common onboarding paths:

1. Create or use an existing Meta Business Portfolio.
2. Complete required business verification steps when applicable.
3. Create the WABA during Embedded Signup or via Meta business tooling.
4. Add and verify phone numbers under the WABA.

For Dualhook customers, Embedded Signup is the standard path because it automates ID discovery and routing setup.

Access and Permissions

WABA management depends on Meta roles and task permissions. Without sufficient permissions, users may be unable to:

• View WABA details
• Manage phone numbers
• Update templates
• Configure webhook subscriptions

If something appears missing in UI or API, verify you are in the correct Business Portfolio and that user/system access includes WABA-level permissions.

See Tech Provider Permission for Dualhook-specific access requirements.

Migration and Portability

Before moving numbers or changing providers:

• Confirm whether the target flow supports number migration for your current account state.
• Review template and webhook impacts before cutover.
• Keep the same ownership context where possible to reduce approval and permission friction.

Treat WABA/number migration as a controlled project, not a same-day toggle.