How to Set Up WhatsApp Business API in India: A 2026 Step-by-Step Guide

If you've been running your business on the WhatsApp Business app and your team is starting to drown — replies piling up, can't broadcast to more than 256 contacts, no way to integrate the inbox with your CRM — you're at the doorstep of the WhatsApp Business API.

The bad news: it's not a download. It's a programmatic interface, and Meta's onboarding has six steps where most Indian SMBs trip up. The good news: in 2026 it's cheaper, faster, and friendlier than it was in 2023. This guide is the path I'd give a founder who messages me about it.

What WhatsApp Business API actually is (and how it differs from the app)

The WhatsApp Business app is what you download from the Play Store. It's free, runs on a phone, and is meant for a single user manning the inbox. It supports labels, quick replies, away messages, and basic catalogs. It's enough until your message volume exceeds about 50 inbound messages a day or you need more than one team member replying.

The WhatsApp Business API is what you graduate to. It's not an app. It's an HTTP endpoint that lets a server — your CRM, a chatbot, or a tool like Doggu — send and receive messages on behalf of a verified business number. With the API you can:

Reply from many devices and many people simultaneously
Send template messages to thousands of contacts (with consent)
Build chatbot flows
Integrate the inbox with your CRM, ticketing, or analytics
Verify your business with the green checkmark (after enough message volume)

The API is what runs every WhatsApp number that says "typically replies in 1 minute."

Eligibility — the prerequisites you need before starting

Before you click anything, you need:

A registered business — sole proprietorship is fine, but you need a name, address, and an industry classification.
A Facebook Business Manager account — create at business.facebook.com if you don't have one.
A phone number that can receive SMS or a voice call for verification, and is not currently registered on any WhatsApp app (Business or personal). If your existing number is on Business app, plan to migrate it (you'll lose the chat history).
A display name — what customers see at the top of the chat. Must match your registered business or trademark; "Saheli Boutique" works, "Saheli Boutique - Best Sarees in Mumbai" gets rejected.
A website with a privacy policy — Meta checks. If you only have a Linktree, get a basic site live first. Even a one-pager works.
A Meta-approved business verification — passport / Aadhaar / GSTIN / PAN of the business owner. Takes 1–7 days.

If you're missing any of these, sort them first. Submitting a half-ready application is the #1 reason for rejection.

BSP vs Meta Cloud API direct — pick early

You access the API in one of two ways:

Option A: Through a Business Solution Provider (BSP). Companies like WATI, Interakt, Gallabox, AiSensy, and Doggu sit between you and Meta. They manage the technical setup, give you a UI, and charge a monthly platform fee on top of Meta's per-conversation pricing. Setup time: a couple of hours. Monthly cost: ₹2,000–₹7,000 plus conversation costs.

Option B: Meta Cloud API direct. You use Meta's Cloud API endpoint (introduced in 2022, free of platform fees) and build everything yourself — chatbot logic, broadcast scheduler, inbox UI. Setup time: a few days for someone who can write code. Monthly cost: ~₹0 platform fee, just conversation pricing.

Most SMBs should pick A. The platform fee is worth not building an inbox UI from scratch. Pick B only if (a) you have an engineer with a few weeks free or (b) you're going to send tens of thousands of conversations a month and want to skip the BSP markup.

If you go with a BSP that supports Embedded Signup (Meta's one-click flow that pulls your business info, creates the WABA, and provisions your number in 5 minutes), you're done in an afternoon. Embedded Signup launched in 2023 and is now the default — if your BSP doesn't support it, pick another BSP.

The Embedded Signup walkthrough

This is the path most Indian SMBs take in 2026, and it's the one Doggu's onboarding uses.

From your BSP dashboard, click "Connect WhatsApp." A Facebook popup opens.
Log in with the Facebook account that owns your Business Manager.
Pick the Business Portfolio that the WhatsApp number should sit under. (If you don't have one, the popup creates it.)
Enter the display name. Spend 30 seconds here — name changes are painful later.
Pick or add the phone number you want to associate. If it's never been on WhatsApp, you can use it directly. If it's currently on the Business app, you'll be prompted to migrate (data loss warning).
Choose verification method (SMS or voice call). Verify with the OTP.
Pick the messaging tier — start with Tier 1 (250 unique business-initiated conversations per 24h). You'll automatically be promoted as you scale.

Total elapsed time: about 5 minutes if you have all the prerequisites. The number is now live on the Cloud API.

Number provisioning + display name approval

Right after Embedded Signup, your number is in NEW state. Meta runs an automated check (display name, business profile, basic compliance) within an hour. Most pass. Some get flagged.

Common reasons your display name gets rejected:

It contains generic terms ("Best Sarees") instead of your trade name
It includes promotional language ("Sale", "Discount", "Cheap")
It contains location ("Mumbai") instead of just the business name
It mentions a regulated industry without the right license (e.g., "Pharmacy" without a pharmacy license uploaded)

If rejected, you'll get an email. Edit the display name in the BSP dashboard, resubmit, wait again. Plan for 1–3 attempts if you're in a regulated industry.

Webhook setup — receiving inbound messages

The API isn't useful until you can react to incoming messages. Webhooks are how Meta tells your server "a customer just messaged you."

In your BSP dashboard, you typically don't configure this — the BSP handles webhook routing for you. If you're going Cloud API direct, you'll set:

Webhook URL: an HTTPS endpoint your server exposes (e.g., https://yourapp.com/api/whatsapp/webhook)
Verify token: a random string you make up; Meta echoes it on first call
Subscribed events: at minimum messages (incoming messages) and message_status (delivery / read receipts)

Send a test message from your personal WhatsApp to your business number. The webhook should fire within a few seconds. If it doesn't, the most common causes are: webhook URL not HTTPS, the verify token mismatch, or the webhook returning a non-200 status.

Common rejection reasons (and fixes)

Aside from display-name rejections above, these kill applications:

Business verification failed because uploaded documents don't match the business name. Fix: re-upload with a document that exactly matches the BM's registered name.
Phone number is on a personal WhatsApp account. Fix: delete the personal WhatsApp account on that number first, wait 30 minutes, retry.
Privacy policy URL on website doesn't load. Fix: make sure it's a real, live page — Meta does fetch it.
Display name violates trademark. Fix: pick a name that's clearly yours, not generic or close to a known brand.

Pricing breakdown — per-conversation cost in INR (2026)

Meta charges per conversation, not per message. A conversation is a 24-hour window opened by either you (business-initiated) or the customer (user-initiated).

Indian rates for 2026:

Conversation category	Cost (INR)
Service (user-initiated, no template)	Free for the first 1,000/month, then ~₹0.30
Utility (order updates, alerts)	~₹0.30 per conversation
Authentication (OTP)	~₹0.10 per conversation
Marketing	~₹0.65 per conversation

A typical SMB sending 5,000 marketing conversations + 5,000 utility per month spends about ₹4,750 on conversation fees, plus the BSP platform fee.

There's no per-message cost inside a conversation — you can exchange dozens of messages within the 24h window for the same fee. This rewards depth: solve the customer's problem inside one conversation rather than sending repeated outbound prompts.

Frequently asked questions

Do I lose my chat history when migrating from WhatsApp Business app to API?

Yes. Meta does not transfer chat history when a number moves from the Business app to the API. Export your chats from the app first if you need an archive. Once on the API, all new conversations are visible in your BSP/Doggu inbox.

Can I have the same number on the Business app and the API?

No. A phone number can only be active on one WhatsApp surface at a time — Business app, API, or personal. Pick one.

How long does the full setup take?

If your prerequisites are ready: an afternoon. If you're starting from "I don't have a Business Manager," about a week (mostly waiting for business verification). Plan for 3–7 days end-to-end.

Do I need GST registration?

For the WhatsApp setup itself, no — Meta doesn't require GSTIN. But if you're billed by an Indian BSP, they'll ask for it to issue a GST-compliant invoice and let you claim ITC.

Can I send marketing broadcasts to anyone?

No. Marketing templates can only go to contacts who have opted in — you must have a record of consent (a check-box on your website, an opt-in keyword reply, etc.). Sending without consent gets your quality rating dropped fast and triggers bans.

If this is the "stuff you need to know" layer and you're now ready to actually do the setup, the easiest path is Doggu's Embedded Signup — it walks you through every step above and runs the BSP plumbing for you. Start your WhatsApp setup with Doggu →