WhatsApp Business API Integration: A Guide for Indian Businesses

WhatsApp Business API integration means connecting WhatsApp to your own software, such as your website, app, CRM or order system, through Meta’s WhatsApp Cloud API. You can connect directly to Meta or go through a provider. Once connected, your systems can send order updates, OTPs and offers using pre-approved templates, and reply to customers within a 24-hour window, all charged per delivered message.

Most pages ranking for this topic are providers selling their own dashboard. This guide is written from the builder’s side: how the API works, the rules that shape what you can build, how Meta charges since its 2025 pricing change, and what a reliable integration needs. Every rule links to Meta’s developer documentation or WhatsApp’s own policy. Meta updates these rules often, so check the linked pages before you launch.

What is the WhatsApp Business API?

It is the programmable side of WhatsApp for businesses, now officially called the WhatsApp Business Platform. Messages are sent and received through the Cloud API, which Meta hosts. The older On-Premises API, which businesses ran on their own servers, stopped working on 23 October 2025, so all new integrations use the Cloud API.

How it differs from the apps you may already use:

Should you connect directly or use a provider?

There are two routes, and both use the same Cloud API underneath.

• Direct to Meta. You create a Meta business portfolio, add a phone number and build the integration against the Cloud API yourself or with a development partner. You own the code and the data flow, and pay Meta directly. This suits businesses that want WhatsApp inside their own CRM, app or order system.
• Through a Solution Provider. A Meta partner handles onboarding and gives you a dashboard, shared inbox, campaign tools and often a chatbot builder. It’s faster to start, but you work within their product and usually pay a platform fee as well as Meta’s charges.

A common middle path is to use the Cloud API directly for transactional messages triggered by your own systems, such as order confirmations and OTPs. A provider’s inbox then handles marketing and support. Either way, the business portfolio and phone number should be registered in your own company’s name, so you keep control if you change suppliers.

What rules shape what you can build?

Four rules decide most design choices.

1. Opt-in comes first. WhatsApp’s Business Messaging Policy says you may only contact people who have given you their number and opted in to receive messages from you. You must also honour opt-out requests. Collect opt-in in your own checkout, sign-up or app with clear wording for each type of message. Under the DPDP Act this is also a consent question, which our DPDP compliance checklist covers.

2. Templates start conversations, and need approval. A template is a message written in advance, with placeholders such as name or order number, which Meta generally reviews before you can use it. Templates fall into three categories:

• Marketing: offers, announcements and abandoned-cart reminders.
• Utility: order confirmations, delivery updates and appointment reminders.
• Authentication: one-time passwords.

3. The 24-hour customer service window. When a customer messages you, a 24-hour window opens, and it resets each time they message again. Inside it you can reply with free-form “service” messages: text, images, documents, buttons, lists and more. Once it closes, you can only send templates again.

4. Messaging limits. A new business portfolio can start conversations with 250 unique users in any rolling 24 hours. Verifying your business is one way to raise that to 2,000. After that Meta scales it automatically to 10,000, 100,000 and unlimited, as long as message quality stays high and you use at least half your current limit over 7 days. Quality is judged on how users react, including blocks and reports. Spammy marketing can therefore hold back your order updates too.

How does Meta charge for WhatsApp messages?

Since 1 July 2025, Meta charges per delivered message, not per conversation. Messages customers send you are free. What you pay depends on the message category and the recipient’s country.

What changed on 1 October 2026. Meta resumed charging for two kinds of message that had been free. Many guides still describe them as free:

• Service messages (free since November 2024) are now free only for the first 1,000 each month per business phone number. Without a payment method on your Messaging account, Meta stops delivering them once that free allowance is used.
• Utility templates sent inside an open customer service window (free since July 2025) are now charged at the normal utility rate.

One exception is still worth designing around. If a customer messages you from a Click to WhatsApp ad on Android or iOS and you reply within the service window, a free entry point window opens. For up to 7 days, Meta doesn’t charge for marketing, utility, authentication or service messages to that customer.

Meta publishes current rates per country in its rate cards, including INR. Indian businesses billed directly by Meta, and providers whose billing country is India, must move their Messaging accounts to INR billing by 31 December 2026. After that date Meta stops delivering messages from non-INR accounts of eligible customers. If you use a provider, ask how they pass these charges on.

What does a reliable integration need?

From the development side, a production-ready integration usually includes:

1. A verified business portfolio and a phone number for the API. If the number is already in use on the WhatsApp Business app, check Meta’s phone number guidance for your options before you start.
2. Templates designed with your product team. Write them early, because approval can delay launch. Keep each template to one clear purpose and the right category.
3. A webhook endpoint. Meta sends incoming messages and delivery and read statuses to your server as webhooks. Your server should check the X-Hub-Signature-256 header on every request, respond quickly, and process events in a queue so slow work doesn’t cause timeouts and retries.
4. Idempotent processing. Webhooks can arrive more than once or out of order, so store each message ID and ignore duplicates. Otherwise a customer could, for example, receive the same OTP or order update twice.
5. Opt-in and opt-out stored with the customer record. Keep when and how each person opted in, and respect “STOP” and other opt-out requests across every system that can trigger a message.
6. Secure token handling. Keep the access token on the server, never in the website or app code, and rotate it if staff or suppliers change.
7. A fallback channel. For OTPs and critical alerts, decide what happens if WhatsApp delivery fails, such as falling back to SMS or email.
8. Monitoring. Track delivery failures, template rejections and your quality rating, so problems show up before your messaging limit is affected.

If you are adding WhatsApp alongside online payments, the same principles apply as in our payment gateway integration guide: trust your server, not the browser, and confirm events through signed webhooks.

Planning your WhatsApp integration

Start with the messages your customers actually want, such as order updates, appointment reminders or OTPs, and design opt-in, templates and the 24-hour window around them. Add marketing once your quality rating is established. If you want WhatsApp connected to your own website, app or CRM, our web development team builds Cloud API integrations, webhooks and the admin screens around them. Get in touch to discuss what you need.