How Do You Connect WhatsApp Business API to Your Website? A Straight Walkthrough

The short version: connecting WhatsApp Business API to your website means getting a verified Meta Business Manager account, choosing a Business Solution Provider (or applying for Meta’s own Cloud API directly), creating a business profile, wiring up a webhook, and then embedding either a click-to-chat button or a full chat widget on your site. Most small businesses spend two to four weeks on verification alone, and a fair chunk of them do not need the full API at all.

I have set this up for clients three times now, and I have watched one of them get rejected twice before Meta approved it. So let me save you the guesswork.

WhatsApp Business API vs the free app: know which one you need first

Before anyone touches a webhook, work out which product you’re talking about, because “WhatsApp on my website” means three different things depending on who’s saying it.

WhatsApp Business App – free, one phone, one device, fine for a sole trader answering messages personally. You just put a wa.me/447700900000 link on your site.
WhatsApp Business Platform (the API) – what most people mean when they say “the API.” No app inbox by default, multiple agents can reply, you can automate, and you pay per conversation.
Third-party inbox layered on top – a BSP like Twilio, 360dialog, Gupshup, or MessageBird gives you a screen to read and send the messages, because the raw API has none.

Here’s the bit most agencies skip past: if you’re handling under 30-40 WhatsApp conversations a day, the free app with a well-placed click-to-chat link on your site does the same job for zero pounds. I’ve seen small businesses talked into a full API build costing £2,000 to £5,000 in setup fees when a £0 wa.me link and a decent business profile with the right logo and description would have covered them for another two years of growth.

What you need before you start

Meta will not let you skip any of these, so gather them first rather than discovering gaps halfway through:

A registered business with proof of existence (Companies House number in the UK, or equivalent) that matches your display name closely
A dedicated phone number that has never been registered on regular WhatsApp (or you’re prepared to lose access to it there)
A Meta Business Manager account, verified
A Facebook Business Portfolio with an admin who can approve the verification requests
Your website live, with a privacy policy, because Meta checks this during business verification

Step by step: connecting the API to your website

1. Set up and verify your Meta Business Manager

Go to business.facebook.com, create a Business Portfolio if you don’t have one, then submit for business verification under Security Centre. Meta checks your legal business name, address, and phone number against public records. This step is where things go wrong most often. My client, a mid-sized furniture retailer, got rejected on the first attempt because their Companies House name was “Oakridge Furniture Ltd” but their display name request was “Oakridge Home.” Second submission with matching names cleared in six days.

2. Choose your route: Meta Cloud API direct, or a BSP

Meta hosts the Cloud API itself now, so you no longer need your own servers (that requirement disappeared back in 2022). You can technically apply for direct access through Meta’s developer platform. In practice, most businesses go through a Business Solution Provider because Meta’s own tooling gives you no proper inbox, no team assignment, no chat history search. The common BSPs:

Twilio – usage-based, good documentation, popular with developers building custom integrations
360dialog – roughly €39 to €59 per month per number plus Meta’s conversation fees, popular in Europe
Gupshup, Infobip, Vonage, MessageBird – similar model, differ mostly in support quality and existing CRM integrations

If you already run HubSpot, Zoho, or Salesforce, check their native WhatsApp connectors first. It’s often cheaper to add WhatsApp as a channel inside a CRM you’re already paying for than to bolt on a separate BSP subscription.

3. Register your phone number and create your business profile

Inside the BSP dashboard (or Meta’s own onboarding if going direct), you register the dedicated number, verify it by SMS or call, then build your profile: business name, category, short description, address, and profile photo. This is your shop window inside the chat, so treat it with the same care you’d give a logo and profile setup for any messaging platform. A blurry logo or a generic “Company” category makes people question whether the account is even real.

4. Apply for message templates

Anything you send outside a 24-hour customer reply window must use a pre-approved template. Meta reviews these, usually within minutes to a few hours, sometimes longer if the wording looks promotional or vague. Templates get rejected for things like unclear opt-in language or missing business context, so write them plainly and get someone outside your team to read them before submission.

5. Configure the webhook

This is the actual “connect it to your website” part. A webhook is a URL on your server that Meta sends incoming message data to (as JSON), and that your system uses to send replies back through the API. You (or your developer) need to:

Build or install an endpoint that receives POST requests from Meta
Verify the webhook with the token Meta gives you
Subscribe to the message events you want (incoming messages, delivery status, read receipts)
Connect that endpoint to whatever handles the reply, whether that’s a live agent inbox, a chatbot, or your CRM

If none of that sentence made sense, this is the point where you hire a developer or a BSP that ships a hosted webhook so you never touch the raw code. Most small businesses go this route, and it’s the right call.

6. Add the actual chat entry point on your website

Once the backend works, you need a way for site visitors to start a conversation. Options, roughly in order of effort:

Click-to-chat link or button – simplest, just a wa.me link styled as a button, opens WhatsApp with a pre-filled message
Floating chat widget – a small bubble in the corner of your site, usually provided by your BSP or a plugin, that opens WhatsApp on click
Embedded chat window – the conversation happens inside your site rather than redirecting to WhatsApp, more technical, needs the full API and webhook working first

For most small business sites, the floating widget is the sweet spot: it looks integrated, costs little to add, and doesn’t require you to build a custom chat interface from scratch.

7. Test end to end before you tell anyone it’s live

Send yourself a message from an outside number, check it lands in your inbox or CRM, reply, confirm it arrives back on WhatsApp, then test what happens outside business hours. I’ve seen businesses launch this and only discover a week later that out-of-hours messages were vanishing into a webhook nobody was monitoring.

What it costs, in real numbers

This is where a lot of guides go vague, so here’s what you’re paying for, roughly, as of 2026:

Meta’s conversation-based pricing: charged per 24-hour conversation window, split into categories (marketing, utility, authentication, service). Rates vary by country; in the UK, marketing conversations sit somewhere around £0.05 to £0.06 each, utility and authentication are cheaper, and service conversations (customer-initiated) are often free for a set volume each month before small charges kick in. Check Meta’s current rate card before you budget, because these change.
BSP monthly fee: anywhere from £0 (some charge only usage) to around £50-£70 per number per month for a mid-tier plan with a proper inbox
Setup and integration cost: if you hire someone to build the webhook and website widget, expect £500 to £2,500 for a straightforward small business build, more if it needs to talk to a custom CRM or booking system
Ongoing management: someone has to answer the messages, which is a staffing cost more than a software one

Compare that to the free WhatsApp Business App plus a click-to-chat link, which costs nothing beyond the phone and your time. The API earns its keep once you’re running automated replies, multiple agents, or integrating WhatsApp into a bigger system like a booking platform where a customer can confirm an appointment straight from a WhatsApp thread. Below that threshold, it’s an expensive way to do the same job.

The uncomfortable bit nobody in this space likes to say out loud

The green verification badge, the “Official Business Account” tick that used to be almost automatic for verified businesses, is now invite-only. Meta tightened this a while back, and unless you’re a large brand with volume that Meta actively wants on the platform, you will very likely never get it, no matter how you complete every verification step. Several agencies still sell “official WhatsApp API setup with verified badge” as a package, and that promise is, for the vast majority of small business clients, not something they control or can guarantee. If someone quotes you for the badge as a deliverable, ask them to show you three clients under 50 employees who got it in the last twelve months. I have never seen it.

Where this fits into a wider automation setup

Once the connection is live, the real value shows up when WhatsApp stops being an isolated inbox and starts feeding into the rest of your business, order confirmations pulling from your shop system, appointment reminders synced with your calendar, FAQ replies handled by a simple bot before a human ever sees the message. That’s the same logic behind most of the useful automation work I’ve seen save hours rather than just look clever, and it applies just as well to a WhatsApp setup as to email or booking systems. Before you brief a developer on any of it, it’s worth writing down exactly what you want the connection to do, because “add WhatsApp to my website” means something different to every developer who reads it. A short written brief covering your goals, volumes, and existing tools will save you three rounds of revisions later.

If you’d rather not run this project yourself, this is squarely the kind of scoped, technical-but-not-huge job an AI consultant working with small businesses handles in a couple of weeks rather than a couple of months, largely because they’ve already sat through the Meta verification rejections once and know which details to get right first time.

My own experience with this, warts and all

The furniture retailer I mentioned earlier eventually got their setup live in three and a half weeks from the first application. The delay wasn’t the technical build, that took our developer four days once verification cleared. It was Meta’s business verification queue and the name-matching rejection. Their inbox now runs through Zoho’s WhatsApp connector, one number, three agents, roughly 60 conversations a day at peak, and it’s reduced their missed-enquiry rate because messages no longer sit in one person’s personal WhatsApp Business App while they’re on holiday. That’s the actual win: not the badge, not the “official” label, just messages that don’t get lost. For context on what else is shifting fast in this space, I cover platform changes like Meta’s pricing and policy updates regularly in my weekly small business AI news roundups, because Meta does not announce these changes loudly and you’ll otherwise find out when your bill jumps.

One more practical note before you build anything: keep a spreadsheet of which tools touch your WhatsApp data, because between the BSP, your CRM, and whatever chatbot layer you add, it’s easy to end up paying three subscriptions for overlapping functionality. I keep a running list of what I pay for and why in my small business AI toolkit rundown, and WhatsApp integrations are one of the most common places I see duplicate spend creep in.

Frequently asked questions

Do I need a developer to connect WhatsApp Business API to my website?

For the webhook and backend, yes, almost always, unless your BSP or CRM offers a no-code connector. For the front-end chat button or widget, no, most BSPs give you a copy-paste snippet that any website builder can handle.

How long does WhatsApp Business API setup take?

Budget two to four weeks from application to a working live connection, mostly waiting on Meta’s business verification. The technical build itself usually takes three to seven days once verification clears.

Is WhatsApp Business API free?

The API access itself has no licence fee from Meta, but you pay per conversation once you exceed the free service-conversation allowance, plus a monthly fee to whichever BSP or CRM gives you the inbox and webhook tooling, typically £0 to £70 a month per number.

Can I just put a WhatsApp link on my website without the API?

Yes, and for most small businesses under roughly 30-40 daily conversations, a free wa.me click-to-chat link tied to the standard WhatsApp Business App does the same job without any of the setup cost or verification wait.

Sources worth reading

WhatsApp’s own Help Centre

Published and maintained by the Lilach Bullock team, covering marketing, AI and business growth.