Back to all guides
Getting Started• 7 min read•12 January 2026

WhatsApp Cloud API Setup: Step-by-Step Without a Developer

Connect a number to Meta's WhatsApp Cloud API using Embedded Signup: prerequisites, OTP verification, tokens, webhooks and your first test message.

Cloud API Setup Embedded Signup

Meta's Cloud API is hosted by Meta itself — there is no server to maintain, no Docker container, no on-premise upgrade window. Here is the full path from zero to first message.

1. Free the phone number

The number must not be registered on WhatsApp Messenger or the WhatsApp Business app. If it is, open that app → Settings → Account → Delete my account first, and wait a few minutes.

2. Run Embedded Signup

Inside your platform, click Connect WhatsApp. Meta's popup asks you to:

  • pick or create a Business Portfolio,
  • create the WhatsApp Business Account (WABA),
  • enter the display name and category,
  • verify the phone number over SMS or voice call.

Embedded Signup returns the WABA ID, phone number ID and a long-lived token automatically — you never copy-paste credentials from Meta's dashboard.

3. Understand the display name rules

Your display name must relate to your business and cannot be a generic word or a URL with promotional text. "Tizyy Support" is fine, "Best Offers 50% Off" is not. Rejected names delay everything, so keep it to your brand plus one function word.

4. Add billing

Attach a card to the WABA. Meta authorises a small amount and then bills on a threshold. A missing funding source is the single most common reason a first campaign silently fails.

5. Subscribe to webhooks

Webhooks deliver inbound messages and delivery/read receipts. Your platform normally subscribes for you; verify that the messages field is checked so the shared inbox actually receives replies.

6. Send the first template

Create a simple utility template:

"Hi {{1}}, your order {{2}} is confirmed. We'll notify you when it ships."

Send it to your own number. If it lands, check three things in your logs: message ID, status delivered, and status read. All three flowing means your webhook is wired correctly.

Troubleshooting the four errors you will actually see

  • #131030 recipient not in allowed list — the WABA is still in test mode; complete verification.
  • #132000 template param mismatch — you passed fewer variables than the template defines.
  • PHONE_NOT_READY / NON_EXISTS — display name review is still pending; wait for approval.
  • #100 permission error — the token is missing the whatsapp_business_management scope; re-run signup.

Once the test message is delivered, migrate one real notification flow (order, booking or OTP) before you touch marketing.

Put this into practice with TIZYY

Official Meta Cloud API, template builder, campaigns, flow automation and a shared team inbox — live in minutes.

Keep reading

Next guide
WhatsApp Business API: The Complete 2026 Guide for Indian Businesses