On this page
What the WhatsApp Business API actually is
The WhatsApp Business API — officially the WhatsApp Business Platform — is Meta’s interface for sending and receiving WhatsApp messages from software instead of from a phone. Today almost every new setup uses the Cloud API, which Meta hosts, so there is no WhatsApp server for you to run. Your application talks to Meta over HTTPS, and Meta calls your application back through webhooks when a customer replies, a message is delivered or a template changes status.
It is different from the free WhatsApp Business app on a phone. The app is designed for a person replying by hand. The API is designed for systems: chatbots, CRMs, order notifications, shared team inboxes and anything else where messages need to be triggered, logged or answered by software.
Signs your business is ready for the API
You don’t need the API to have a WhatsApp presence. You need it when one phone and a few people can’t keep up, or when WhatsApp has to connect to other systems. Typical signs:
- A real estate agency running Click-to-WhatsApp ads where enquiries arrive faster than agents can answer them from one handset.
- A clinic that wants appointment confirmations and reminders sent automatically from its booking software.
- A D2C brand sending order, dispatch and delivery updates from its store platform.
- A coaching institute where several counsellors need to reply from one official number with a shared history.
- A SaaS startup that wants to send one-time passwords or account alerts over WhatsApp.
If any of these sound familiar, an official API setup is the foundation everything else is built on — chatbots, notification systems and CRM sync all need it first.
What we handle during onboarding
- Meta Business account review — checking that your business portfolio in Meta Business Manager is set up correctly and helping you through business verification, which needs documents that match your registered business details.
- Number selection and registration — choosing a new number or migrating an existing one, and registering it to your WhatsApp Business Account.
- Display name approval — submitting a display name that follows Meta’s naming guidelines so it is less likely to be rejected.
- Message template drafting and submission — writing the utility, marketing and authentication templates you actually need, in the right category, and resubmitting if any are rejected.
- Technical connection — access tokens, webhook endpoint, signature verification and a small service that sends and receives messages reliably.
- Handover documentation — where every setting lives, who has admin access and how to add templates later.
The rules that decide what you can send
Most disappointment with WhatsApp automation comes from not understanding the platform’s rules at the start. We explain them plainly before anything is built:
- Opt-in is required. You may only message people who have agreed to receive WhatsApp messages from your business. A purchased or scraped list is not opt-in.
- The 24-hour customer service window. When a customer messages you, you can reply freely for 24 hours after their last message.
- Approved templates outside the window. Any business-initiated message — a reminder, an update, a promotion — must use a template Meta has approved.
- Quality rating and messaging limits. Meta tracks how recipients react to your messages. Blocks and reports lower your quality rating, and new numbers start with limits on how many people they can message each day.
Meta charges for certain messages, and both its pricing model and its policies change from time to time. We point you to Meta’s current documentation rather than quoting figures that may be out of date by the time you read this.
How the setup runs, step by step
- Short discovery call — what you want to send, to whom, and from which systems.
- Account audit — we check your Meta Business portfolio, admin access and any previous WhatsApp setup.
- Verification and registration — documents, number and display name submitted, with follow-up on any queries from Meta.
- Templates — a first set drafted, reviewed with you and submitted.
- Connection and testing — webhooks wired up, test messages sent in both directions, delivery statuses confirmed.
- Handover — access, documentation and a walkthrough for your team.
We connect directly to the Cloud API or through a Business Solution Provider if you already use one — the choice depends on whether you want your own integration or a ready-made inbox product.
What affects timeline and cost
The technical connection is usually the predictable part. Waiting on Meta is not. The main factors:
- How quickly business verification clears, which depends on your documents matching your business details exactly.
- Whether the number is new or being migrated from an existing WhatsApp account.
- How many templates you need and whether any are rejected and need rewording.
- Whether messages must connect to existing software such as a store, booking system or CRM.
For a scoped estimate, tell us what you want to send.
Common mistakes to avoid
- Using an unofficial tool first and moving to the API only after the number has been banned.
- Registering a personal number that the owner still needs for everyday calls and chats.
- Submitting promotional wording as a utility template — it is likely to be rejected or re-categorised.
- Giving admin access to one person only, so the business is locked out when that person leaves.
Our WhatsApp automation guide covers these and more in detail, and the full range of what we build on top of the API is on the WhatsApp Automation page.
Frequently asked questions
Do I need the WhatsApp Business API or is the free app enough?
If one or two people reply by hand and nothing needs to connect to other software, the free app is often enough. You need the API for chatbots, automated notifications, a shared multi-agent inbox or CRM integration.
Can I keep using my existing WhatsApp number?
Usually yes, by migrating it to the API. The number then generally stops working in the normal app, so we plan the switch carefully and confirm that nothing else depends on it.
Will I get the green tick?
The blue verified badge is granted by Meta at its own discretion, and nobody can guarantee it. A properly verified business with an approved display name is what you need to send messages; the badge is optional.
Why was my message template rejected?
Common reasons are wrong category, promotional content in a utility template, unclear placeholders or formatting that breaks Meta’s guidelines. We reword and resubmit rejected templates as part of the setup.
Can I message all my existing customers once the API is live?
Only those who have opted in to WhatsApp messages from you, and only with approved templates outside the 24-hour window. Sending to people who haven’t agreed is the fastest way to lower your quality rating.
Talk to us about whatsapp business api integration
Official Meta Cloud API setup, number verification and message template approval handled for you.