Skip to content

WhatsApp API Onboarding

Also called: WhatsApp Business API onboarding · WhatsApp API setup · how to get WhatsApp Business API · WhatsApp API go-live

The end-to-end path from a Meta business portfolio to the first sent WhatsApp API message: accounts, number, display name, payment, webhooks and templates.

Reviewed

What is WhatsApp API onboarding?

WhatsApp API onboarding is the full sequence a business goes through to start messaging customers on the WhatsApp Business Platform through the Cloud API — from having a Meta business portfolio to seeing the first message delivered. It spans several Meta assets and approvals: the business portfolio (managed in Meta Business Suite), optional but important business verification, a WhatsApp Business Account (WABA), a phone number with an approved display name, a payment method, a webhook that receives messages and statuses, and at least one approved message template.

Since Meta's new account model rolled out from 23 September 2026, the WABA appears as two linked accounts: a WhatsApp account (WAAC) that holds the phone number and business identity, and a Messaging account that holds templates, billing and webhook subscriptions and keeps the familiar WABA ID. Existing API calls are unchanged, so onboarding still looks the same to developers, but Meta Business Suite now shows WhatsApp Accounts and Messaging Accounts tabs.

Most businesses onboard through a partner's Embedded Signup, which creates or selects the portfolio, accounts and number in one guided flow and shares them with the partner's app. Embedded Signup is only part of onboarding, though: someone still registers the number on the Cloud API, subscribes the app to webhooks, adds a payment method or credit line, and gets templates approved. A developer building a direct integration does the same steps from the App Dashboard instead.

Key takeaways

  • WhatsApp API onboarding is the whole path from a Meta business portfolio to the first message sent through the Cloud API.
  • It covers the portfolio, business verification, the WhatsApp and Messaging accounts, a number, its display name, payment, webhooks and templates.
  • Embedded Signup automates the account and number steps; registration, webhooks, payment and templates still have to be finished after it.
  • New portfolios start with a messaging limit of 250 unique users per 24 hours and a cap of two phone numbers; verification raises both.
  • The first business-initiated message must be an approved template; free-form replies need an open 24-hour customer service window.

See InfiQ pricing

Interactive stop

Trace the path from portfolio to first message

8 / 8
Business portfolioMeta Business Suite
Business verificationlifts 250 limit, 2-number cap
WhatsApp + Messaging accountvia Embedded Signup
Number added + OTPSMS or voice code
Display namereviewed by Meta
POST /registermessaging_product + pin
Payment methodor partner credit line
WebhooksPOST /subscribed_apps
Approved template sentsent → delivered → read
  • Business portfolio to Business verification: submit documents
  • Business verification to WhatsApp + Messaging account: signup flow
  • WhatsApp + Messaging account to Number added + OTP: pick a number
  • Number added + OTP to Display name: name review
  • Display name to POST /register: register on Cloud API
  • POST /register to Payment method: billing
  • Payment method to Webhooks: subscribe app
  • Webhooks to Approved template sent: first template

Hop 8 of 8

WebhooksApproved template sentfirst template

Arrives at Approved template sent — sent → delivered → read.

Nine stops from a Meta business portfolio to a delivered template. Watch the packet travel each step in order; the Embedded Signup stops are the first row, everything after it still has to be done.

Hop 8 of 8: Webhooks to Approved template sent — first template.

How does WhatsApp API onboarding work?

  1. Prepare the business portfolio and verification

    Create or reuse the business portfolio in Meta Business Suite and submit business verification. It is not needed to start, but it lifts the 250 messaging limit and the two-number cap.

  2. Create the accounts and add a number

    Through a partner's Embedded Signup or the App Dashboard, create the WhatsApp and Messaging accounts, pick an eligible number and verify it with an SMS or voice code.

  3. Set the display name and register the number

    Submit a display name that matches your brand, then call POST /{PHONE_NUMBER_ID}/register with messaging_product and a six-digit pin. Registration allows 10 attempts per 72 hours.

  4. Add payment and subscribe to webhooks

    Attach a payment method to the Messaging account (or a partner's credit line), then POST /{WABA_ID}/subscribed_apps and point your app's webhook URL at a server that verifies signatures.

  5. Get a template approved and send

    Submit a utility or marketing template, wait for the automatic review (up to 24 hours), then send it to an opted-in customer and watch the sent, delivered and read statuses arrive.

WhatsApp API onboarding in code

# 1. Register the verified number on the Cloud API
curl -X POST "https://graph.facebook.com/v26.0/{PHONE_NUMBER_ID}/register" \
  -H "Authorization: Bearer {ACCESS_TOKEN}" \
  -H "Content-Type: application/json" \
  -d '{ "messaging_product": "whatsapp", "pin": "{SIX_DIGIT_PIN}" }'
 
# 2. Subscribe your app to the account's webhooks
curl -X POST "https://graph.facebook.com/v26.0/{WABA_ID}/subscribed_apps" \
  -H "Authorization: Bearer {ACCESS_TOKEN}"
 
# 3. Send the first approved template
curl -X POST "https://graph.facebook.com/v26.0/{PHONE_NUMBER_ID}/messages" \
  -H "Authorization: Bearer {ACCESS_TOKEN}" \
  -H "Content-Type: application/json" \
  -d '{
    "messaging_product": "whatsapp",
    "to": "919830012345",
    "type": "template",
    "template": {
      "name": "order_confirmed",
      "language": { "code": "en" },
      "components": [
        { "type": "body", "parameters": [ { "type": "text", "text": "SW-1042" } ] }
      ]
    }
  }'

The pin becomes the number's two-step verification PIN. Store it safely: registration allows only 10 attempts in 72 hours.

WhatsApp API onboarding: key facts and limits

Starting messaging limit
250 unique users per rolling 24 hours (business portfolio)
Starting phone number cap
2 per business portfolio, 20 after verification
Register endpoint
POST /{PHONE_NUMBER_ID}/register, 10 attempts per 72 hours
Webhook subscription
POST /{WABA_ID}/subscribed_apps
Template review
Automatic, up to 24 hours
Default throughput
Up to 80 messages per second per number
Billing
Per delivered message by category: marketing, utility, authentication, service

Why does WhatsApp API onboarding matter?

Onboarding is where most WhatsApp projects lose time. A launch can sit for days because business verification was never started, the chosen number is already on someone's WhatsApp, the display name was rejected, no payment method was added or a webhook was never subscribed. Seeing the whole path in order lets a business owner know which steps it must do personally, lets a developer know what to automate, and lets both plan around the parts that are reviews by Meta rather than work they control.

Example: A Kolkata sweet shop goes live in two days

A family-run sweet shop in Kolkata wants order confirmations on WhatsApp before Durga Puja. On day one the owner completes a partner's Embedded Signup with its existing business portfolio and a new mobile number bought for WhatsApp, enters the SMS code, and submits the display name matching its signboard. The partner registers the number, subscribes its app to the Messaging account's webhooks and asks the owner to add a payment method, which she does from Meta Business Suite. A utility template, order_confirmed, is approved within the hour. On day two the shop sends its first confirmation; the webhook reports delivered and then read. Business verification, submitted the same day with the shop's trade licence, arrives a week later and lifts its messaging limit above the starting 250.

— A Kolkata sweet shop goes live in two days

Common mistakes with WhatsApp API onboarding

  • Starting business verification last

    Verification is the slowest step and the one that lifts the 250 limit and the two-number cap. Submit it on day one, with documents that match the portfolio's legal name.

  • Treating Embedded Signup as the finish line

    A completed signup still needs registration, a webhook subscription, a payment method and an approved template. Track each as a separate onboarding step.

  • Choosing a number that is already on WhatsApp

    Registration fails while the number is active in WhatsApp or the Business App. Use a fresh number, delete the old account or connect it through coexistence.

  • Forgetting the payment method

    Charged messages fail without a payment method or credit line on the Messaging account. Add it before the first send, not after the first error.

  • Sending free-form text first

    Outside a customer service window only templates are delivered. Start with an approved template; free-form replies work once the customer writes back.

WhatsApp API Onboarding FAQs

How long does WhatsApp Business API onboarding take?+
From an hour to a couple of weeks. The account, number and template steps can be done in a day; business verification and display-name review are Meta reviews that can take longer.
Do I need business verification to start using the WhatsApp API?+
No, but you will want it. Unverified portfolios start at a 250 unique-user messaging limit and a cap of two numbers; verification is one of the ways to lift both.
What is the difference between onboarding and Embedded Signup?+
Embedded Signup is one guided flow inside onboarding. It creates the accounts and verifies the number; onboarding also includes registration, payment, webhooks, templates and the first send.
What does a business need before starting WhatsApp API onboarding?+
A Meta business portfolio, an eligible phone number it owns, a display name that matches its brand, a payment method, and its legal documents for business verification.

Best practices for WhatsApp API onboarding

  • Collect the legal name, address, website and GST or registration certificate before you begin; verification needs them.
  • Write two or three templates you need at launch and submit them as soon as the account exists.
  • Send the first live messages to your own team's numbers and confirm the webhook statuses before going to customers.

Talk to InfiQ

From definition to your first message

InfiQ is an official Meta Business Partner. Start a 7-day free trial — no card needed — and see this running on your own number.

Start free trialBrowse all 550 terms