How Do You Connect WhatsApp Business API To Your Website

The short version: you don't connect the WhatsApp Business API to your website directly, you go through a Business Solution Provider (Meta calls them BSPs), get your number verified, then drop a click-to-chat link or widget on your site that opens a conversation. The free app on your phone can't do this, you need the API tier, and most small businesses pay somewhere between 30 and 300 pounds a month depending on message volume before they've written a single reply.

Why this trips people up before they even start

I ran social media for brands from 2005, and the WhatsApp Business API is the first channel I've watched where the tool itself is invisible. You never log into "WhatsApp API" the way you log into Facebook Ads Manager. There's no dashboard with a green logo waiting for you. Instead you're signing up with a provider, and the provider is what puts the chat widget on your website. I had a client email me last year asking why she couldn't find "the WhatsApp Business API app" in the app store. There isn't one. That's the first thing to get straight, because it changes who you need to talk to.

The three things you need before you touch your website

First, a Meta Business Manager account, verified with your actual business details, not a personal profile with a business name bolted on. Second, a phone number that has never been used on WhatsApp or WhatsApp Business before, because the API takes it over completely and you lose the ability to use the regular app on that number. Third, a provider. The official term is Business Solution Provider, and Meta approves them directly. You don't apply to Meta for API access on your own unless you're a large enterprise running your own infrastructure, which almost nobody reading this is.

Picking a provider without wasting a month

This is where most people lose time. There are dozens of providers and they all say roughly the same thing on their homepage. What differs is pricing structure, template approval speed and whether they give you a proper widget builder or just an API you're expected to wire up yourself. If you've got a developer on staff, the API-only route is cheaper long term. If you don't, pay for the provider with a visual widget builder, it's worth the extra 20 or so pounds a month the first year alone.

Step by step: getting the widget live

1. Create or confirm your Meta Business Manager account and verify the business (this alone can take three to five working days if Meta asks for extra documents, so start it first).
2. Choose a provider and complete their onboarding, which links your Meta Business Manager to their platform.
3. Add and verify your dedicated WhatsApp number through the provider's console, usually by SMS or voice code.
4. Submit your message templates for approval if you plan to send anything outside a live conversation, such as order confirmations. Approval usually lands within a day, sometimes within minutes.
5. Generate your click-to-chat link or embeddable widget code from the provider dashboard.
6. Paste the widget snippet into your website. On WordPress that's usually Appearance, then Theme File Editor or a plugin's own settings screen, never edit core files directly. On Shopify it's Online Store, then Themes, then Edit Code, and you drop the snippet just before the closing body tag.
7. Test the full flow yourself from a phone that isn't your business number, so you see exactly what a customer sees.

If you want the simplest possible version and you're not ready for a paid provider, WhatsApp itself gives you a plain click-to-chat link with no API involved: wa.me/ followed by your full phone number in international format, no plus sign, no spaces. Put that behind a button and it opens WhatsApp with your number pre-filled. It won't automate anything, but it works today, for free, and it's honestly where most small businesses should start before they pay for the API tier at all.

Where this gets uncomfortable

Here's the bit the sales pages skip. The API charges per conversation, not per message, and Meta's pricing has shifted more than once since it launched. A "conversation" is a 24 hour window, so if a customer messages you five times in one day about the same order, that's one conversation, but if they come back tomorrow with a new question, that's a second one. Providers add their own margin on top of Meta's conversation fee, which is where the 30 to 300 pounds a month range comes from. I've seen businesses budget for messaging volume based on their email list size and get a nasty surprise when WhatsApp reply rates turned out to be three or four times higher than email open rates. People treat WhatsApp like texting a friend, they reply fast and they reply often, and every one of those replies inside a fresh 24 hour window can trigger a new billable conversation depending on your provider's rules.

What to put on the widget once it's live

Don't just slap "Chat with us" on the button. I tell every client the same thing: name the person, not the department. "Chat with Sarah about your order" converts better than "Customer Support" because WhatsApp is a personal channel and people expect a person on the other end, not a ticket number. Set your business hours honestly in the provider's auto-reply settings too. Nothing kills trust faster than a chat that looks live at 2am and goes silent for nine hours.

A quick example from my own setup

When I first tested this for a client's e-commerce site, we used a provider with a visual builder, had the widget live within two working days once the number was verified, and set an automated first reply that answered the three questions people asked most: shipping time, returns policy and whether a product was in stock. That single automated message cut their manual replies by roughly a third in the first month, because most people just wanted the answer, not a conversation. That's the real value of the API over the free click-to-chat link, the automation on the first touch.

Security and verification details worth knowing

Meta requires your business to complete verification before you can send template messages at scale, and that includes confirming your business name matches what's shown to customers exactly, down to punctuation. If your legal name is "Smith & Co Ltd" but your website says "Smith and Co", fix that mismatch before you submit for verification, it's one of the most common rejection reasons. You'll also need a green checkmark option available for larger, well known brands, but most small businesses won't get that and don't need it to operate normally.

The mistake I see most often

People connect the API, get the widget live, and then never touch the automated flows again. The API supports quick reply buttons, list messages and even simple flows for booking or ordering, but providers bury these features three menus deep because the headline feature is always "you're now on WhatsApp." Go into your provider's automation or chatbot builder section in the first week and set up at minimum a welcome message and an away message. That's the difference between a widget that just opens a chat window and a channel that does work while you sleep.

What happens if Meta rejects your verification

It happens more than providers admit. The two most common rejection reasons are a business name mismatch (your Companies House name and your website name need to line up, or at least clearly relate) and a website that doesn't show enough proof the business is real, no address, no clear description of what you sell, nothing linking the domain to the entity applying. Fix your site's footer and about page before you submit, not after a rejection email lands. Resubmission usually gets a decision within a few days, but I've seen it take two weeks when documents bounce back and forth over a bank holiday.

Who this is worth it for

If you get fewer than twenty messages a week, skip the API entirely and use the free click-to-chat link, save your money. The API earns its cost once you've got a team member (or several) needing shared access to one business number, or once automated replies are saving real hours, not just looking clever. I've watched businesses jump straight to the paid tier because a sales call made it sound essential, then use precisely none of the automation features for six months. Start free, upgrade when the volume demands it, not before.

I have written more around this on the site: How Do You Connect WhatsApp Business API to Your Website? A Straight Walkthrough, How to Close Down a Facebook Business Page (Without Losing Data You’ll Want Later), WhatsApp Help: 43 Guides to Transfers, Backups, Business and Privacy.

Related: the api page.

Related: the web development page.

Frequently asked questions

Can I use my personal WhatsApp number for the Business API?

No. The API requires a dedicated number that has never registered with WhatsApp or WhatsApp Business before, and once it's on the API you can't also use the standard app on that same number.

How much does WhatsApp Business API cost per month?

There's no flat licence fee from Meta, you pay per conversation plus your provider's platform fee. Small businesses typically land between 30 and 300 pounds a month depending on volume and which provider they pick.

Do I need a developer to add the widget to my website?

Not if you choose a provider with a visual widget builder. You paste one snippet of code into your site's theme editor or a plugin field, no custom development required for a standard chat button.

What's the difference between the free click-to-chat link and the paid API?

The free wa.me link just opens a chat with your number pre-filled, no automation, no analytics. The paid API adds automated replies, message templates, multiple team members answering from one number and reporting on response times.