How to get the WhatsApp Business API in India

“WhatsApp Business API” is not a product you buy from an app store, and it is not the green WhatsApp Business app you already have on your phone. It is Meta’s messaging infrastructure, and getting onto it means going through Meta’s own verification — either yourself, direct, or through a company that does the paperwork and runs the platform for you.

Both paths end at the same messaging infrastructure. What differs is who verifies your business, who you pay, and how much of the setup you do yourself. This page is written for the business owner deciding between those two paths, not the developer reading Meta’s own docs — if that is you, Meta’s Cloud API documentation is the better next stop.

The API is not the app, and that distinction decides everything else

The WhatsApp Business app is the free download — one phone, one person answering, a green tick and nothing else. The WhatsApp Business API (officially the WhatsApp Business Platform) is what a business uses once more than one person needs to answer, once messages need to be sent by software, or once volume passes what a single phone can handle. There is no in-app upgrade button between them: moving to the API means registering your number on different infrastructure entirely, and — in most cases — removing it from the app first.

Two consequences follow directly from that:

Your number cannot be active on the personal or Business app when you register it on the API. If it is currently running your day-to-day WhatsApp, you either deregister it first or use Meta’s newer Coexistence option, which lets eligible businesses keep the app running on the same number while the API also connects to it. Coexistence is not available to everyone yet, so check it before assuming you can keep both.

The number has to be reachable by SMS or a voice call, because that is how Meta verifies it during registration. Mobile and landline numbers both work; a virtual or VoIP number is rejected unless it is on Meta’s own approved list, so check that before you commit a number you cannot easily replace.

What you need before you start

Eligibility is less about qualifying and more about having the paperwork ready, since almost any registered business can apply. In practice you need:

• A Meta Business Portfolio (formerly Business Manager) — the account Meta verifies, not your personal Facebook login.
• A dedicated phone number, not currently active on the WhatsApp consumer or Business app, that can receive an SMS or voice call.
• A legal business name, address, phone number, email and website that match each other exactly — the single most common reason verification gets rejected is a mismatch between what you typed into the Business Portfolio and what your supporting documents actually say.
• Two or three supporting documents proving the business name and address — a certificate of incorporation, GST registration, a business licence, or a recent utility bill in the business’s name are the usual set.
• A display name that follows Meta’s naming rules (your real business name, not a slogan or a domain), which gets reviewed separately once the business itself is verified.
• A published privacy policy URL the API integration can point to.

None of this is unusual paperwork for a registered business — it is the same kind of documentation a bank or a payment gateway asks for. What trips people up is exactness, not difficulty: Meta’s rejection message is a generic “we couldn’t verify your business,” with no line-by-line explanation of what didn’t match.

The verification steps, in the order Meta actually runs them

1. Create the Meta Business Portfolio and fill in the business information section completely before submitting anything — an incomplete profile is a common, avoidable rejection reason.
2. Submit Meta Business Verification — upload your supporting documents and wait for Meta to confirm the business is real and that you are entitled to represent it.
3. Create or connect a WhatsApp Business Account (WABA) once the business itself is verified.
4. Register your phone number to the WABA and complete the SMS or voice-call check.
5. Submit your display name for review — a separate approval from business verification, and it can be rejected on its own even after the business passes.
6. Get your first message templates approved. Anything that is not a free-form reply inside an open conversation window has to be a Meta-reviewed template before it can be sent.
7. Start sending — capped at 250 business-initiated conversations in any rolling 24 hours until the business is fully verified, after which the ceiling rises with your messaging quality and history.

If you are going through a BSP rather than applying yourself, most of steps 1–4 happen inside their onboarding flow (Meta’s own Embedded Signup), which removes the developer-facing parts but not the underlying verification — Meta still has to approve your business regardless of who is holding your hand through the form.

How long it actually takes — not the SLA, the real experience

The mechanical steps, once your documents are genuinely ready and match exactly, typically run two to four days for business verification, a few hours for WABA and number registration, and 24–48 hours for your first template approvals — three to ten business days end to end is the number that shows up most often in vendor onboarding guides.

That number assumes your first submission is clean. In practice, it rarely is. The single biggest cause of delay is not Meta being slow — it’s a name, address or phone number that doesn’t match precisely between the Business Portfolio and the documents behind it, which Meta rejects without saying which field. The advice from people who have been through repeated rejections is consistent: change one specific thing per resubmission and track what you changed, rather than resubmitting the same documents hoping the second attempt gets a different reviewer. Reapplying blindly five or eight times in a row tends to slow things down further rather than speed them up, and a business with a generic or recently registered name has more of these cycles to get through than one with a long-standing GST history and a matching digital footprint.

The honest range to plan around, if this is your first attempt: a few days if your paperwork is already internally consistent, one to three weeks if it takes a rejection or two to get there. Budget the longer number and be pleasantly surprised, rather than the other way round.

What Meta itself charges

Since 1 July 2025, Meta bills per message delivered, not per conversation — the older conversation-based model is retired. Messages fall into three billable template categories, and a fourth that is currently free:

• Marketing templates — promotional sends, billed on every delivery.
• Utility templates — order updates, appointment reminders and the like.
• Authentication templates — OTPs and login codes.
• Service messages — free-form replies inside an open 24-hour conversation window, and utility templates sent inside that same window, which are currently free.

For India, third-party rate trackers reading Meta’s own published rate card put a marketing message at roughly ₹0.86 each, and a utility or authentication message at roughly ₹0.12 each, both exclusive of GST (myoperator.com, “WhatsApp Business API Pricing in India”, read 2026-09-09). Meta’s rate card is published as a downloadable file rather than a page you can quote a URL against, so treat these as indicative rather than exact — check Meta’s own pricing documentation for the current card before budgeting against it.

Meta’s messaging charges are treated as an imported digital service (OIDAR) for Indian GST purposes, so the standard 18% GST applies on top, under reverse charge if you’re the registered business receiving the service — your BSP may handle the filing for you or may leave it to you, and that is worth asking before you sign anything.

A change worth planning around now, since it lands soon. From 1 October 2026, Meta is ending the blanket free status for both service messages and in-window utility templates. Each phone number keeps 1,000 free service messages a month; the 1,001st onward is billed at the same per-message rate as utility and authentication templates, and the monthly allowance does not roll over. Utility templates sent inside an open conversation window lose their free-in-window status entirely under the new rules (Wati, “WhatsApp Service Message Pricing Changes Explained”; YCloud, “WhatsApp API Pricing Update: Effective October 1, 2026”, both read 2026-09-09). If a quote you’re comparing was priced before this date, it is about to get more expensive regardless of which vendor you pick — that is Meta’s change, not a markup any provider is adding.

What a BSP charges on top — and it is usually two things, not one

A BSP (Business Solution Provider) is a Meta-approved company that handles the technical integration, gives you an inbox or CRM to manage conversations from, and — depending on the vendor — either bills you directly for Meta’s messaging charges with a markup, or keeps your billing relationship with Meta and charges purely for its own platform (a Tech Provider, a related but distinct Meta partner tier). Either way, going through one is close to universal in India: Meta does not offer its own customer-facing dashboard, so almost nobody talks to the raw Cloud API by hand.

Two separate charges are worth telling apart, because a single “per-message” headline number usually hides one of them:

1. The platform fee. A recurring subscription for the inbox, the integrations and the account itself, independent of how many messages you send. Reading four Indian and international platforms’ own pricing pages on 2026-09-08 (Wati, AiSensy, Interakt, Gallabox): Wati’s tiers run from roughly ₹2,499 to ₹9,999 a month; Interakt’s from about $55 to $69 a month plus taxes; Gallabox’s from just under ₹3,000 to nearly ₹17,000 a quarter — roughly ₹1,000 to ₹5,700 a month, on the same monthly basis as the other two — depending on plan. AiSensy does not publish a platform-tier table on its pricing page at all — only add-on products and per-message rates — which is itself worth knowing before you request a quote from them.

2. The per-message rate, which is frequently marked up above Meta’s own. AiSensy publishes ₹1.09 per marketing message and ₹0.145 for utility or authentication; Interakt publishes ₹0.958 and ₹0.150 respectively — both above the roughly ₹0.86 and ₹0.12 Meta itself charges. That gap is the BSP’s margin on the pass-through, and it is rarely broken out as a separate line on a sales page — it just shows up as “our rate,” which reads as the whole cost when it is actually Meta’s charge plus a markup.

Sometimes a third: a one-time onboarding fee, separate from the monthly subscription — commonly ₹0 where it’s folded into the first month, up to roughly ₹20,000–₹25,000 for a vendor that does the display-name and template setup for you rather than leaving you to do it. Whether this is charged, and how much, varies enough between vendors that it is worth asking for explicitly rather than assuming it is included.

Put together: two quotes that both say “WhatsApp Business API” can differ by several times their all-in monthly cost depending on whether the platform fee is high with cheap messages, or low with marked-up messages — the same asymmetry that shows up comparing AI receptionist quotes in what an AI receptionist actually costs in India. Ask for the platform fee and the per-message rate as two separate numbers, every time.

Where Kooday sits

Kooday is a BSP-model provider, not a bring-your-own-API developer tool. WhatsApp is one of the channels bundled into our plans — see the pricing page for the current figures, since we keep prices in one place rather than restating them here where they would go stale.

Two things about how we handle the two charges above, stated plainly because most quotes in this market blur them:

We don’t mark up Meta’s own messaging charges. They stay in your own account and are billed to you at cost — the same principle we apply to telephony, covered in what an AI receptionist actually costs in India. You see Meta’s own rate on your own invoice, not ours with a margin folded in.

Onboarding is part of getting set up, not a separate line you negotiate. We handle the Meta Business verification, the WABA and number registration, the display name submission and your first template approvals as part of setup — you are not filling in the Business Portfolio yourself while also trying to run a business.

What this guide is not about: if a campaign-sending tool for your existing, opted-in contacts is what you actually want, that is a priced feature on our own plans (see pricing) — not what this page covers. This page is about getting the API itself and an assistant that answers enquiries on it. Read WhatsApp enquiries are piling up faster than you can reply for what we cover on the answering side, and judge for yourself whether that is the right fit before talking to us.

If your interest in the API is specifically a chatbot on WhatsApp, or automating replies more broadly, the WhatsApp chatbot and WhatsApp automation hub pages go into that in more depth than this page does.

What to do with this

If you are choosing between applying yourself and going through a provider: applying yourself saves the platform fee and the message markup, and costs you the verification paperwork, the ongoing template management, and building or buying an inbox to actually manage conversations from — none of which the API gives you for free. Most businesses land on a provider for exactly that reason; the API on its own is infrastructure, not a product a non-developer can use directly.

Whichever path you take, ask for the platform fee and the per-message rate as two separate numbers before you compare anything, budget for the 1 October 2026 pricing change if you’re pricing this out now, and expect the verification step to take longer than the official estimate the first time your documents don’t match exactly — because for most businesses, that is what actually happens.