Currently accepting new projects
WhatsApp API integration connects WhatsApp to the software you already run: your website, booking system, CRM or a chatbot. Done the official way, it lets a team share one number, send order and appointment updates automatically, and answer common questions round the clock. Here is how the pieces fit, what Meta asks of you, and what to prepare before anyone writes code.
The short answer: WhatsApp API integration means connecting the official WhatsApp Business Platform (the Cloud API, hosted by Meta) to your own systems. Your server sends messages through the API and receives customer replies and delivery updates through a webhook. You need a Meta business portfolio, a WhatsApp Business Account, a phone number with an approved display name, and pre-approved templates for any message you send first.
The WhatsApp Business Platform has no app for you to install. It is an API: a set of web addresses your software calls to send messages, and a webhook that Meta calls to tell your software what happened.
Outgoing: your system sends a message
Incoming: the customer replies
The same webhook also reports message statuses such as delivered and read.
Meta now hosts the API for everyone. The older self-hosted On-Premises API reached its end on 23 October 2025, according to Meta's sunset notice, so any new integration should use the Cloud API.
Most integrations start with one job and add more later. Filter by the kind of business you run:
Confirmation, dispatch and delivery messages sent automatically from your store when the order status changes.
Utility templatesAppointment, class or site-visit reminders from your booking system, with buttons to confirm or reschedule.
Fewer no-showsAnswers timings, prices, location and order status any time, and hands over to a person when it cannot help.
Inside the 24-hour windowEnquiries from your website button or ads land in your CRM with the chat attached, so no lead sits on someone's phone.
Send a payment link from your gateway and a receipt once it clears, both triggered by your system.
One-time passwords for customer logins or app sign-ups, sent as authentication templates.
Pairing the API with an AI assistant is increasingly common; our guide to ChatGPT for small business covers where that helps and where it does not.
Before a single message goes out, a few accounts and settings have to exist. Meta's Cloud API get-started guide walks through them.
Your business's home in Meta's business tools. Business verification here unlocks higher limits.
The account that holds your phone numbers, templates and billing for WhatsApp messaging.
A number you own that can receive an SMS or call for verification, plus a display name Meta reviews.
A developer app with the WhatsApp use case, and a long-lived token from a system user, stored securely.
A secure HTTPS address on your server where Meta sends incoming messages and status updates.
Pre-approved messages, categorised as marketing, utility or authentication, for anything you send first.
Templates are reviewed before use. Meta checks the category immediately and rejects a template filed in the wrong one, so write order updates as utility and offers as marketing. The category also decides the price; see WhatsApp Business API pricing.
In Meta's developer dashboard, create an app with the WhatsApp use case and connect it to your business portfolio.
Meta gives you a test number and a temporary token. Send test messages to your own phone before touching your real number.
Register your business number, verify it by SMS or call, and submit the display name.
Create a system user token with the WhatsApp permissions, and point the webhook at your server.
Connect your website, CRM or booking system so the right event triggers the right template, and route replies to an inbox or bot.
Get templates approved, add a payment method in Meta's billing, then start with a small group of opted-in customers.
This is usually the first worry. The answer depends on which app the number is on today. Meta's guide to using an existing WhatsApp number sets out two routes.
Meta's developer documentation adds that messages you send from the Business app in this shared setup stay free, while API messages are billed at Cloud API rates. Still deciding between the apps? Our comparison of WhatsApp vs WhatsApp Business helps.
Source: Meta's messaging limits and phone numbers documentation, as of November 2026. Meta changes these rules; check the pages before you plan a campaign.
Replies to customers who message you first are not capped by the messaging limit, which is another reason a fast-answering inbox or chatbot pays off.
Before you start a WhatsApp API integration
All done.
You can connect to the Cloud API directly with Meta and build your own inbox, or use a Business Solution Provider (BSP) that offers a ready-made dashboard for a monthly fee. Both are official. Direct gives more control; a BSP gives a faster start.
Avoid "WhatsApp API" tools that work by scanning a QR code with your phone, bulk senders and modified apps. They are not the official platform, break WhatsApp's terms, and are a common route to a banned number. If that has already happened, read what to do when a WhatsApp Business account is banned.
We are not a BSP or a Meta partner. We build and connect the integration on your own Meta account or with the provider you pick, and the account stays in your name. See our AI and automation services or how we automate customer service.
It is connecting the official WhatsApp Business Platform (Cloud API) to your own software, such as a website, CRM, booking system or chatbot. Your system sends messages through the API and receives replies and delivery updates through a webhook.
No. Setting it up has no Meta fee, but Meta charges per delivered template message by category, and replies inside the 24-hour window have a monthly free allowance per number. Providers may add their own fees.
Yes. You can delete the WhatsApp account on that number and register it on the API, losing old chats, or, for a WhatsApp Business app number, onboard through a provider that supports keeping the app running alongside the API.
For a direct Cloud API setup, yes: someone has to handle tokens, webhooks, templates and the connection to your systems. A BSP dashboard reduces the coding, but connecting it to your own website or CRM still needs technical work.
New business portfolios start with a messaging limit of 250 for messages you send first in a rolling 24 hours. It can rise to 2,000 through one of Meta's scaling paths, such as verification or steady high-quality sending, and higher with good-quality messaging. Replies to customers are not capped by this limit.
The app is a free phone app for one business number and a few devices. The API is a platform with no app of its own, built to connect WhatsApp to software, support teams and automation, and charged per message.
We set up the official Cloud API, directly with Meta or through the provider you choose, and connect it to your website, CRM or chatbot with webhooks and sensible templates. Get a fixed quote within one business day on our AI and automation page.
Get a fixed quoteAI and automationOnly to see which pages help and which don’t. Nothing is sold, nothing is used for advertising, and declining changes nothing about how the site works. More in our privacy policy.