--- title: "How to Set Up WhatsApp Business API for Your Business: A Step-by-Step Guide" description: "A practical, end-to-end guide to setting up the WhatsApp Business API in 2026 — from Meta Business portfolio and phone number to Embedded Signup, verification, templates, webhooks and your first broadcast." author: "Ilayaraja S" pubDate: 2026-08-26 canonical: "https://www.convo.co.in/blog/how-to-set-up-whatsapp-business-api/" --- # How to Set Up WhatsApp Business API for Your Business: A Step-by-Step Guide Most guides to the WhatsApp Business API stop at "contact a provider." That is not much help when you are the person who actually has to get a number live, get templates approved, and send the first campaign without getting throttled. This is the whole path, in the order you will walk it. For most small and mid-sized businesses it takes somewhere between an afternoon and about a week. The variable is almost never the technical work — it is Meta's Business Verification queue. ## First, know what you are signing up for The WhatsApp Business API — Meta now brands the whole thing the **WhatsApp Business Platform** — is not an app you install. It is a messaging interface that sits on top of a phone number you own, and it is what you need once you have outgrown the free WhatsApp Business app. Three things change the moment you move to the API: - **No phone, no app.** The number lives on Meta's Cloud API. Your team works out of a web dashboard — a [shared inbox](https://convo.co.in/#features) — instead of one handset someone has to physically hold. - **Unlimited agents.** Any number of people can answer the same number at once, with routing, tags and assignment rules. - **You pay per message, and you have to use templates.** Any conversation *you* start must use a message template Meta has pre-approved. Free-form replies are only allowed inside a 24-hour window after the customer writes to you. If you are not yet sure the API is the right tier for you, read [WhatsApp Business App vs WhatsApp Business API](/whatsapp-business-app-vs-whatsapp-business-api/) first. Moving a number onto the API is reversible, but it is a nuisance, and it is worth being sure. One piece of history still trips people up: there used to be two flavours of the API, **On-Premises** and **Cloud**. On-Premises was sunset by Meta in October 2025. If a vendor is still pitching you a self-hosted WhatsApp gateway in 2026, that is a red flag. Everything below assumes Cloud API, because it is the only thing that exists now. ## What you need before you start Gather these first. Nearly every stalled onboarding we see is stuck on one of them. | Requirement | Detail | | --- | --- | | A phone number you control | Can receive an SMS or voice OTP. Must **not** be currently active on the WhatsApp or WhatsApp Business app. | | A Meta Business portfolio | Formerly "Business Manager." Free to create at business.facebook.com. | | Business registration documents | GST certificate, Certificate of Incorporation, Udyam registration, or equivalent — for Business Verification. | | A website with your business details | Must show your business name and, ideally, a contact number and address that match your documents. | | A business email on your own domain | Meta treats `you@yourbrand.com` very differently from `yourbrand@gmail.com`. | | A display name | The name customers will see. Meta checks it against your registered business name. | ### About that phone number This is the single most common false start. The number you want on the API **cannot already be registered on the WhatsApp app or the WhatsApp Business app**. If it is, you have two options: 1. Delete the WhatsApp account on that number first (Settings → Account → Delete my account), wait for it to clear, then use it. You will lose the chat history and the contacts on that number. 2. Use a fresh number for the API and keep the old one running on the app. A landline or toll-free number works, as long as it can receive the voice OTP. Plenty of Indian businesses run their API number on a dedicated SIM that nobody ever puts in a handset. ## Step 1 — Create and organise your Meta Business portfolio If you already run Facebook or Instagram ads, you almost certainly have one. Use it; do not create a second. Meta's verification, messaging limits and quality history are increasingly tracked at the **portfolio** level, so consolidating is in your interest. Inside the portfolio, check three things: - Your **legal business name** field matches your registration documents *exactly* — including "Private Limited" versus "Pvt Ltd." - Your address and phone number match those documents. - You have **admin** access, not just employee access. You cannot complete this process as an analyst. ## Step 2 — Start Business Verification early Do this **now**, in parallel with everything else, because it is the step with a queue attached. Meta reviews the documents you upload and confirms your business is a real, registered entity. In Business Settings → Security Centre → Start Verification, you upload one document proving legal existence (Certificate of Incorporation, GST certificate, Udyam certificate) and one proving your address or phone (a utility bill, bank statement, or the same document if it carries both). What gets people rejected: - The name on the document does not match the portfolio name character-for-character. - A cropped, screenshotted, or photographed-at-an-angle document. Upload clean PDFs. - A website that does not mention the business name on the document. - An address that appears nowhere on the website. Turnaround is usually a couple of business days, occasionally two weeks. You can keep building while you wait — you just cannot scale past 250 conversations a day until it clears. More on that in [WhatsApp messaging limits and quality rating](/whatsapp-messaging-limits-and-quality-rating/). ## Step 3 — Connect the number through Embedded Signup Here is where a provider comes in. You *can* go direct to Meta as your own Tech Provider, but that means building against the Cloud API yourself, hosting a webhook endpoint, and building your own inbox, template manager and campaign tool. For almost every business that is not a software company, the economics do not work. Working through a provider like Convo, the flow is: 1. You sign in to the provider's dashboard and click "Connect WhatsApp." 2. A Meta-hosted popup — **Embedded Signup** — opens. This is Meta's own window, not the provider's; you log in with your own Facebook credentials. 3. You select (or create) your Business portfolio and your WhatsApp Business Account (WABA). 4. You enter your **display name** and business category. 5. You enter the phone number and verify it with the OTP. 6. You grant the provider permission to send and receive on that number. That is genuinely it. Embedded Signup is the default onboarding path for all new WhatsApp Business Platform accounts, and it typically takes five to ten minutes end to end. When you are done you have a live WABA, a registered phone number, and — importantly — you still own it. The WABA sits in *your* Business portfolio. A provider can be swapped out; you never hand over the asset.
A quick test of any provider: ask whether the WABA will be created inside your own Meta Business portfolio. If the answer is anything other than "yes," you are renting a number rather than owning one, and migrating away later will be painful.
In Convo, one connected number becomes a **Project**. Everything you do afterwards — send a message, submit a template, run a campaign, subscribe to a webhook — is scoped to that project's `project_id`, which you will find in Settings → Project Details or in the dashboard URL. ### Getting the display name right Meta reviews your display name and rejects it if it does not clearly relate to your business. The safest choice is your registered business name or your well-known brand name. Avoid: - Generic words alone — "Support," "Offers," "Sales." - A URL or phone number as the name. - Descriptors Meta reads as promotional — "Best Deals," "Official 100%." A rejected display name does not block you permanently; you simply submit another. But each round costs a day, so get it right the first time. ## Step 4 — Set up your profile and two-step verification Small step, real impact on trust. In your dashboard, fill in: - Profile photo (your logo, square, at least 640×640) - Business description - Category - Address, email, and website Then enable **two-step verification** with a six-digit PIN and store that PIN somewhere your whole team can find it. You will need it if you ever migrate the number, and Meta requires it before you can apply for the green tick. ## Step 5 — Create and submit your first message templates Templates are the part people underestimate. Every business-initiated message — every order update, every campaign, every OTP — is a template Meta approved in advance. Templates fall into three billable categories. Convo's dashboard and Template API label them `TRANSACTIONAL`, `MARKETING` and `OTP`, which map to Meta's utility, marketing and authentication: - **Utility / `TRANSACTIONAL`** — tied to an existing transaction. Order confirmations, shipping updates, appointment reminders, payment receipts. - **Authentication / `OTP`** — one-time passcodes and login verification. - **Marketing / `MARKETING`** — everything promotional. Offers, launches, re-engagement, cart recovery. Start with the four or five you know you will send constantly, not a speculative campaign. Approval is typically minutes to a few hours. Two rules save most of the pain: put every variable in a placeholder like `{{1}}` rather than hard-coding a name, and never submit a template whose category is obviously wrong (a discount code filed as utility will be re-categorised or rejected). If you would rather submit templates from your own systems, Convo exposes `POST /project/{project_id}/wa_template`; a successful call returns the template with `status: "PENDING"` until Meta reviews it. The full ruleset, including the rejection reasons behind most failures, is in [WhatsApp message templates: categories, approval rules, and how to stop getting rejected](/whatsapp-message-template-approval-guide/). ## Step 6 — Wire up automation and your inbox With the number live, decide what happens when a customer writes in at 11pm. - **Welcome message and away message.** The bare minimum. Set expectations rather than leaving silence. - **A chatbot for the top five questions.** Order status, pricing, location, hours, human handoff. In Convo you build these in a drag-and-drop flow builder and watch them run in the live chat dashboard — no code. - **Routing rules.** Send billing queries to one team, sales to another. - **Canned replies.** The 20 answers your agents type every day. Then set up the escalation path. Bots that cannot hand over to a human are the fastest way to earn a block, and blocks feed straight into your quality rating. ## Step 7 — Wire up webhooks, if you are integrating If you plan to react to delivery receipts, read receipts and inbound replies in your own systems, subscribe a webhook now while everything else is fresh. Convo delivers events by HTTP callback to a URL you own; each subscription carries a **shared secret** you use to verify that a payload genuinely came from Convo. You can list what is subscribed with `GET /project/{project_id}/webhook`. The message-status flow is: you send, the API returns a message ID, and delivery, read and reply events arrive on your webhook referencing that ID. If you are not integrating with back-office systems yet, skip this step — the dashboard shows the same events. ## Step 8 — Import contacts, with consent You need **opt-in** before you message anyone. Meta requires that customers have agreed to receive messages from you on WhatsApp, and that they knew it was your business they were agreeing to. Valid opt-in sources: a checkbox at checkout, a "WhatsApp me updates" toggle on your form, a customer who messaged you first, a click-to-WhatsApp ad, a QR code scan at your counter. Not valid: a purchased list, or a database of numbers collected years ago for a different purpose. When you import, bring your attributes with you — city, plan, last purchase date, course, segment. In Convo, contacts are stored with E.164 phone numbers and custom attributes, and every attribute you import becomes a filter you can broadcast on later. Segmented campaigns are the difference between a 60% click rate and a block. ## Step 9 — Send a controlled first campaign Do not open with 5,000 messages. New numbers start at a low tier and Meta watches your first sends closely. A sane first week: 1. Send to 50–100 of your warmest contacts — recent buyers, active customers. 2. Watch delivered, read and reply rates for 24 hours. 3. Check your quality rating in the dashboard. Green means proceed. 4. Roughly double your volume each send while quality holds. Use at least 50% of your current daily limit consistently and Meta moves you up the tiers on its own — 250 to 1,000 to 10,000 to 100,000 to unlimited. Programmatically, the pattern in Convo is two steps: link an approved template to a named campaign with `POST /project/{project_id}/campaign/api`, then send it to contacts through the Send Campaign endpoint. Configure once, send repeatedly. ## Step 10 — Send your first message from code (optional) If you are integrating directly, the smallest possible test is one authenticated call. From Settings → API & Integrations, copy your **Project API Password**, then: ```bash curl -X POST \ https://connect.api-wa.co/project-apis/v1/project/{project_id}/messages \ -H "X-API-WA-Project-API-Pwd: YOUR_API_PASSWORD" \ -H "Content-Type: application/json" \ -d '{ "to": "9170XXXXXXXX", "recipient_type": "individual", "type": "text", "text": { "body": "Hello from the API" } }' ``` Phone numbers carry the country code with **no `+`**. A plain text message like this only reaches someone who messaged you in the last 24 hours; outside that window you must send a template. A successful call returns HTTP 200 with a message ID under `messages[0].id` that later webhook events reference. Auth failures return `401` with `{"name": "ERR401", ...}`; keep the password out of browser JavaScript and mobile binaries. Full details are in the [API documentation](https://doc.convo.co.in/introduction). ## Step 11 — Apply for the green tick, once you qualify The verified badge is a separate application, made after Business Verification is approved and your number is live and in good standing. It is genuinely nice to have — it lifts response rates — but it is **not required** to use the API, and Meta's bar (notability, meaning independent press coverage) is real. The full application path is in [How to get the WhatsApp green tick](/whatsapp-green-tick-verification-guide/). ## Step 12 — Understand what you will be billed Since July 2025 Meta bills **per delivered template message**, priced by category and by the recipient's country. India is one of the cheapest markets in the world for this, which is a large part of why WhatsApp works so well as a channel here. Two things worth planning around now: - Conversations that start from a click-to-WhatsApp ad or a Facebook Page button open a **72-hour free window** in which everything you send, templates included, costs nothing to deliver. - From **1 October 2026**, free-form service replies and utility templates sent inside the 24-hour customer service window stop being free. If your volume is concentrated in support replies, that is a budget change you want to model before it lands. As a rough sense of scale in India: marketing lands under ₹1 per delivered message, utility and authentication around ₹0.10–0.15. Meta updates the country rate card periodically, and the published card is the only authority. ## A realistic timeline | Day | What happens | | --- | --- | | Day 0 | Portfolio tidied, Business Verification submitted, Embedded Signup completed, number live | | Day 0–1 | Profile, two-step PIN, first templates submitted and approved | | Day 1–3 | Chatbot flows, routing, canned replies, webhooks, contact import | | Day 2–10 | Business Verification approved → limit rises to 1,000/day | | Week 2 | Volume ramping, quality rating green, tier 2 unlocked | | Week 3+ | Green tick application, if you meet the notability bar | The technical work is a day. The waiting is the rest. ## Common reasons setups stall - **The number was already on WhatsApp.** Deleted too late, or not at all. - **Display name mismatch.** "ABC Retail" on the portfolio, "ABC Retail Pvt Ltd" on the GST certificate. - **Documents rejected for legibility.** Screenshots instead of PDFs. - **No opt-in.** The first campaign goes to a bought list, block rate spikes, quality goes red in 48 hours, and the account is capped. - **Waiting on the green tick before launching.** You do not need it. Launch, build history, then apply. ## Getting started with Convo Convo is an official WhatsApp Business API provider. Setup runs through Meta's Embedded Signup into your own Business portfolio, includes green tick application assistance, and comes with the broadcast, shared inbox, chatbot and analytics tooling on top — with no per-agent charge, so your whole support team can work the same number. Plans start at ₹2,500/month and include the API connection and green tick application at no extra cost — see [pricing](https://convo.co.in/pricing) for what is in each tier, or read the [API documentation](https://doc.convo.co.in/introduction) if you plan to integrate directly with your own systems. If you would rather have someone walk the setup with you, [book a 30-minute demo](https://calendly.com/suranshu_convo/30min) and we will get your number live on the call. ## FAQ **How long does WhatsApp Business API approval take?** The connection itself takes minutes through Embedded Signup. Meta's Business Verification is the slow part — usually two to five business days, occasionally up to two weeks if documents need resubmitting. **Can I use my existing WhatsApp Business number for the API?** Yes, but you must delete the WhatsApp Business app account on that number first. The chat history on that number does not carry over. **Do I need a Facebook page?** Not strictly for the API itself, but you need a Meta Business portfolio, and a page is required if you want to run click-to-WhatsApp ads — which are one of the cheapest ways to fill the funnel, since they open a 72-hour free messaging window. **Is the WhatsApp Business API free?** The API access is free. You pay Meta per delivered template message, and you pay your provider for the software layer on top. There is no free tier for business-initiated messaging. **Can two businesses share one number?** No. One number maps to one WhatsApp Business Account. Multiple *agents* can share a number — that is the point of the API — but not multiple businesses.