What is WhatsApp Business API integration, in plain terms?
WhatsApp Business API integration is the work of connecting Meta’s official messaging platform to your own software so that sending and receiving WhatsApp messages becomes part of your business process rather than a phone someone carries around. There is no separate app to install; the “API” is a set of web addresses Meta runs, and your system talks to them.
Every integration has three layers. The Meta layer is your business portfolio, your WhatsApp Business account (WABA), your phone number and your approved templates. The glue layer is code: an access token, a service that calls Meta’s send endpoint, and a webhook receiver that Meta calls whenever a customer writes or a message is delivered or read. The business layer is whatever you already run, such as a website, a CRM, a billing tool or a mobile app, which decides when a message should go and what should happen when a reply arrives.
People often say “integration” when they mean only the first layer, getting a number approved on a provider’s dashboard. That is onboarding. A proper WhatsApp Business API integration finishes the job, so that a new lead on your website, a status change in your CRM or a payment in your billing software sends the right message automatically, and the customer’s answer lands in the correct record.
- Meta layer: business portfolio, WABA, number, display name, templates, payment method
- Glue layer: access token, send service, webhook receiver, message log, alerts
- Business layer: the website, CRM, ERP, store or app that triggers and receives messages
Do you need the API, or is the WhatsApp Business app enough?
Stay on the free WhatsApp Business app while one or two people reply by hand and nothing needs to happen automatically. Move to the API when messages must be triggered by your software, when several staff need to work one number with proper records, or when you want replies stored against customer records you control.
The app is excellent for a shop owner answering customers personally. Its limits show when the business grows: WhatsApp’s help centre allows up to four linked devices on one account, labels live only inside the app, and there is no way for your website or CRM to send a message on its own. Broadcast lists only reach people who saved your number.
The API removes those limits but adds rules. Business-initiated messages must use pre-approved templates, and Meta charges per template message delivered. Customers must have opted in to hear from you. For most businesses the switch makes sense once missed chats or copy-paste work start costing real money. Our page on moving from the Business app to the API goes through that decision with examples, and the Hinglish automation guide covers what each option can automate.
Cloud API direct or through a BSP: which WhatsApp Business API integration route is right?
Go direct on Meta’s Cloud API when you have software to connect and someone to maintain the integration; go through a Business Solution Provider (BSP) when you want a finished dashboard and have nothing of your own to wire in. Both routes are official. The message itself travels through Meta’s Cloud API in either case, because Meta hosts the platform.
A BSP adds a layer on top: an inbox, broadcast screens, chatbot builders, analytics and support. You pay for that with a monthly plan, and some providers also add a margin on Meta’s per-message rates. What you give up is control. Your conversations sit in the provider’s system, your automations live in their builder, and moving away means exporting data and migrating the number.
Direct Cloud API integration means Meta bills you for messages and nobody else charges per message. Your WhatsApp Business account lives in your own business portfolio. Your code, running on your own hosting, holds the logic. The trade-off is that you need a developer to build and look after the glue layer, which is exactly the part we do.
Choose Cloud API direct when
You have a website, CRM, ERP or app that should send and receive messages; you want chat data in your own database; message volume is high enough that per-message markup matters.
Choose a BSP when
You want a ready inbox and campaign screen this week, have no in-house software, and prefer paying monthly over owning code.
A mixed route
Some businesses start on a BSP for the inbox and later move the number to direct Cloud API once their own CRM is ready. That is possible, but plan the number migration carefully.
Meta Business verification: what Indian businesses need before integration
Meta Business verification confirms that your business portfolio belongs to a real, registered business. You can start testing the Cloud API without it, but verification is what lifts your early messaging limit and number cap, and the higher limit is what brings your display name up for Meta’s check, so plan it in week one of any WhatsApp Business API integration.
The process runs inside Meta Business Suite under Security Centre. You enter the legal business name exactly as it appears on your registration document, the registered address, a phone number, and a website on a domain you control. Then you upload an official document that shows the legal name and, ideally, the address, and confirm ownership by email to an address on your domain, a phone call, SMS or a domain check. The name on the document, the portfolio and the website footer should match exactly. Small mismatches are the easiest way to fail this check: a trade name on the website but the proprietor’s name on the document, or a free email address instead of one on the business domain.
Before you start, put the legal name and address in your website footer, make sure your domain has working email, and keep a clear scan of your registration document ready. If the business is a proprietorship trading under a brand name, decide which name you are verifying and make the website say the same thing.
- Legal business name identical across document, portfolio and website
- A live website on your own domain, with contact details
- An email address on that domain for the confirmation code
- A clear, uncropped scan of the registration document
- Admin access to the business portfolio for the owner, not only for the developer
Display name approval: getting your brand name shown in chats
The display name is the business name customers see on your WhatsApp profile, and on the Cloud API it goes through its own review. According to Meta’s developer documentation, a number’s display name is checked against Meta’s display name guidelines when the portfolio reaches a higher messaging limit, and every later name change goes through that check again.
Meta shows the review status on each number, such as pending review or declined. Names that pass tend to be the plain brand name the business actually uses, visible on its website, without extra words like “Official”, “Support” or a list of services. A name that has no visible link to the verified business, or that looks like someone else’s brand, is the usual reason for a decline.
In practice we prepare the name before verification: we check that your website shows the same brand name prominently, avoid punctuation and emoji, and keep a second, simpler version ready in case the first is declined. A declined name does not stop the integration technically, but messages will not carry a trusted name until it passes, so it should not be left to the last day. If the aim is the verified badge rather than the name, that is a separate process covered on WhatsApp verified badge for businesses.
Which number to use, and how to move one off the WhatsApp Business app
You can use a fresh number, move your existing Business app number fully to the API, or connect the existing number so it works on both the app and the API. The right answer depends on how much customers already know the old number and whether staff still want to chat from the phone.
Meta’s rules for a Cloud API number are simple: you must own it, it needs a country and area code, and it must be able to receive an SMS or voice call for the verification code. A number that is already registered on WhatsApp cannot be registered on the API until that account is deleted, unless you use the newer route that connects an existing Business app number. New business portfolios can register two numbers at first, rising to twenty after verification or after reaching the 2,000 messaging limit.
The connect-existing-number route, often called coexistence, keeps the Business app working on the phone while the API works in parallel. Meta’s documentation says up to six months of chat history can sync during setup, and the number gets a fixed throughput of 20 messages per second. Some app features change: broadcast lists become read-only, and disappearing messages, view-once and live location are switched off for one-to-one chats. It is onboarded through a Meta partner’s Embedded Signup flow, so ask before assuming it is available for your setup.
Fresh number
Cleanest technically. Best when the API number will be used for notifications and support that start fresh.
Full migration
Delete the Business app account, then register the same number on Cloud API. Chat history on the phone does not come across; export anything you need first.
Coexistence
Keep the phone app for personal chats while your software sends templates. Good for owner-led businesses, with the feature limits above.
Webhooks: how replies and delivery updates reach your database
A webhook is a web address on your server that Meta calls every time something happens on your number: a customer sends a message, a message you sent is delivered or read, or a send fails. In a WhatsApp Business API integration, the webhook receiver is the part that decides whether you ever lose a message.
We build the receiver as a small service with one job: accept the call, check that it genuinely came from Meta by verifying the request signature against your app secret, write the raw event to the database, and reply quickly. Heavier work, such as updating the CRM, running a bot or notifying a salesperson, happens afterwards from a queue. That split matters because a slow receiver causes retries, and retries without care create duplicate records.
Each WhatsApp message carries a unique ID, so the receiver stores events against that ID and ignores repeats. Status events arrive in their own order and can come late, so the log keeps the latest status rather than assuming sent, delivered and read arrive in sequence. Failed-send events carry an error code, and those should raise an alert, not sit quietly in a table. The table below maps the common events to what your system should do with them.
- Verify every request’s signature before trusting it
- Store first, process later from a queue
- Use the message ID to ignore duplicate deliveries
- Alert a person on failed sends and on silence (no events for hours)
- Keep raw events for troubleshooting, trimmed by a retention rule you choose
Template approval: writing messages Meta accepts first time
Any message your business starts, or sends after the 24-hour window since the customer last wrote, must use a pre-approved template. Meta’s template documentation lists three categories, authentication, marketing and utility, and says review can take up to 24 hours, though many templates clear much faster.
Utility templates are tied to something the customer already did: an order, a booking, an invoice, an account change. Marketing templates are anything promotional. Authentication templates carry one-time codes. The category decides the price per message, so a template labelled utility must genuinely read like a transaction update; Meta can re-categorise templates that look promotional.
Templates use variables such as {{1}} or named placeholders like {{first_name}} for the parts your system fills in. Keep variables inside sentences, not at the very start or end, and send a realistic sample value with each one. According to Meta, a business portfolio that is not yet verified can hold up to 250 templates per WhatsApp Business account; verified portfolios with approved display names can hold up to 6,000. Paused or disabled templates are usually a quality problem: people blocking or reporting you. That is a signal to stop sending, not to resubmit with new wording.
Utility example
“Hello {{1}}, we have received your enquiry for {{2}}. Our team will call you on {{3}}. Reply here if the time does not suit you.”
Authentication example
A one-time code with a copy-code button, sent when someone logs in or verifies a phone number on your site or app.
WhatsApp Business API integration with a website
On a website, the API usually does three jobs: confirm an enquiry the moment a form is submitted, send booking or order updates, and deliver login codes. A click-to-chat button needs no API at all, so do not pay for integration if that is all you want.
A good website flow saves the lead first and messages second. The form writes the enquiry to your database, then calls the send service with a utility template that thanks the person and says what happens next. If the send fails, the lead is still safe and someone is alerted. Add an explicit opt-in line near the phone field, for example a checkbox reading “Send me updates about this enquiry on WhatsApp”, and store the time and page of consent with the lead.
For businesses on WordPress or a custom stack, the integration is a small plugin or module calling your own send service, not a heavy third-party widget that slows the page. If you are building or rebuilding the site at the same time, the website itself starts at ₹10,000, and the WhatsApp part is priced as a separate line so you can compare. Stores have their own playbook: Shopify owners should read our Shopify WhatsApp integration guide, and WordPress stores the WooCommerce version.
WhatsApp Business API integration with a CRM, ERP or billing software
Connecting WhatsApp to a CRM means two directions: CRM events send templates out, and customer replies flow back as activities on the right lead or contact. Most of the effort is in matching people correctly and deciding who owns each conversation.
Outbound is the easier half. A deal moving to “quotation sent” can send a utility template with the PDF link; a lead untouched for two days can nudge the assigned salesperson rather than the customer. Inbound needs care. Phone numbers must be normalised to one format (with country code, no spaces) so a reply from 98xxxxxx matches the lead stored as +91 98xxxxxx. New numbers should create a lead with a source tag, not vanish.
Popular CRMs have marketplace extensions, and some of them are fine. We build custom when the extension cannot reach the fields you need, when you want chats stored in your own database as well, or when the CRM is custom-built. For Zoho specifically, see Zoho CRM WhatsApp integration; for billing data and reminders, WhatsApp payment reminders; for accounting, Tally WhatsApp integration. If you do not have a CRM yet and mostly need a team inbox, the WhatsApp CRM guide for small businesses is the better starting point.
Messaging limits and quality rating after you go live
Messaging limits cap how many unique customers you can start conversations with in a rolling 24 hours, and they apply to your whole business portfolio, not each number. Meta’s documentation lists the tiers as 250, then 2,000, 10,000, 100,000 and unlimited.
New portfolios start at 250. Meta gives three ways to reach 2,000: complete business verification, go through a partner-led verification, or deliver 2,000 template messages to unique contacts outside open service windows within 30 days with good quality. Above 2,000, Meta raises the limit automatically when quality stays high and you have used at least half your current limit in the previous seven days.
Quality is driven by how customers react. Blocks and reports lower it; replies and read messages keep it healthy. The integration should respect this: send marketing only to people who opted in, stop sequences once someone replies, honour “stop” requests automatically, and watch the quality rating in WhatsApp Manager during the first weeks. A new integration that fires 2,000 promotional templates on day one at a cold list is the fastest way to get templates paused. For volume sending, the bulk messaging on the official API page covers warm-up and list hygiene.
How much does WhatsApp Business API integration cost in India?
There are two separate bills. The integration itself is a one-time build: with us it starts at ₹40,000 (US$600) for onboarding, one number, the webhook receiver and log, a first set of templates and one connected system. The running cost is Meta’s per-message charges, billed to your own account.
The build price rises with the number of systems you connect, with two-way sync (inbound replies updating records, not only outbound sends), with a custom shared inbox for several agents, and with AI replies. A setup that also needs new software, such as a portal or CRM built from scratch, is quoted with that build; custom software starts at ₹60,000. Hosting for the webhook service is usually small and sits in your own cloud account.
Meta’s side is priced per delivered template message. Since July 2025 Meta has charged per message rather than per conversation, with the rate depending on category and the recipient’s country. Service replies to customers inside the 24-hour window are free, and so are utility templates sent inside an open window, according to Meta’s pricing page. How that adds up for different business sizes is worked through on our WhatsApp Business API cost in India page, including when direct Cloud API works out cheaper than a provider plan.
How long does WhatsApp Business API integration take?
Plan for 2–4 weeks from the first call to live messages. The code is rarely the slow part; Meta’s reviews and your document readiness are.
Week one is paperwork and plumbing. We set up the business portfolio and app with you, submit business verification, register the number, and stand up the webhook receiver on your hosting with a test number. Template drafts go to you for wording approval. Week two is building the connection to your website or CRM, submitting templates, and testing sends and replies end to end with staff phones. Weeks three and four absorb review delays, handle a declined display name or template if needed, and run a small live pilot before full traffic.
You can shorten this. Have the registration document scan, domain email and website footer ready before the first call. Decide in advance which number to use. Name one person who approves template wording. The integration is also faster when the connected system already has an API; an old desktop program with no API adds time for a bridge.
Access tokens, security and customer data
Treat the WhatsApp access token like a bank password: whoever holds it can message your customers in your name. Production integrations use a system user token generated in your own business portfolio, never a developer’s personal login.
We create the system user under your portfolio, give it only the WhatsApp permissions it needs, and store the token in your hosting’s secret manager or environment settings rather than in code. The app secret used for webhook signature checks is stored the same way. If a developer leaves the project, you remove their access in Business Settings and nothing breaks, because nothing depended on their account.
Chat logs hold personal data: names, numbers, sometimes addresses and order details. Keep them on hosting you control, limit which staff roles can read them, and set a retention period that suits your business. India’s Digital Personal Data Protection Act, 2023 applies to how businesses handle personal data, so collect clear consent, use the data for the purpose you stated, and speak to your own adviser about the specifics for your sector. We build the consent capture, access roles and deletion routines; we do not give legal advice.
Red flags when someone offers WhatsApp Business API integration
Most problems come from who owns the account, not from the code. Check these before you pay anyone to set up the WhatsApp Business API for you.
- The WhatsApp Business account is created in the provider’s business portfolio instead of yours
- “No approval needed, send to any number” — that describes an unofficial tool, and numbers get banned
- No mention of opt-in, templates or messaging limits
- Per-message price quoted with no reference to Meta’s published rates
- Chat history only visible in a dashboard with no export
- Access token tied to a developer’s personal Facebook account
- No alerting when webhooks fail, so outages go unnoticed for days
- A promise of the verified badge as part of setup; Meta decides that, not a developer
A trustworthy integrator will happily show you where each piece lives in your own Meta Business Suite at handover. If anything important only exists in their account, you do not fully own your integration.
Worked example: a distributor’s order portal talking to WhatsApp
This is a hypothetical scenario to show how the pieces fit, not a client story. Say a building-materials distributor in Nagpur runs a small custom order portal for about 300 dealers. Dealers phone and WhatsApp the office to ask whether orders are dispatched, and staff copy details between the portal and their phones all day.
We would propose direct Cloud API integration from ₹40,000. Week one: the owner creates the business portfolio with us on a call, submits verification with the firm’s registration document, and chooses a new number for dispatch updates while the office number stays on the Business app. We deploy a webhook receiver next to the portal on its existing hosting. Week two: three utility templates (order received, dispatched with vehicle number, delivered) are submitted, and the portal fires them on status changes. Dealer replies land in a new “messages” table and show on the order screen, with an alert to the dispatch clerk when a dealer asks a question.
Weeks three and four: a pilot with twenty dealers, fixes to phone-number matching for dealers stored without country codes, then rollout. The owner gets a monthly estimate of Meta charges based on order volume. Since most messages are utility updates, and many are sent while a dealer’s chat window is already open, the running cost stays modest. Two months of free maintenance follow the launch, with the scope set out in the written quote.
WhatsApp Business API integration across India
All our integration work is remote, so the process, price and reply times are the same wherever you are. Onboarding happens on a screen-share, testing on staff phones, and payment by UPI or bank transfer against an itemised invoice you can hand to your accountant.
City pages describe the local businesses we build for: Ludhiana, Rajkot, Nagpur, Kozhikode, Madurai, Jodhpur, Bhopal, Vijayawada, Siliguri and Thane. Businesses outside India work with us the same way, billed in USD through Wise, bank wire or PayPal; see countries we work with.
What we do not do: install hardware, visit offices, or run your campaigns day to day. We build the integration, hand it over in your name, and look after it if you want us to.