Channels12 min read

WhatsApp Cloud API: How to Connect It and What You Can Automate

By Anton Schwartz, co-founder of Konverto

In short

  • The WhatsApp Cloud API is Meta's hosted connection for business messaging: software sends messages through the Graph API and receives every customer message as a webhook. Since the On-Premises API expired on October 23, 2025, it is the only API option.
  • To connect it you need a Meta business portfolio, a WhatsApp account and a Messaging account, an app with an access token, a business phone number and an endpoint or provider inbox where incoming messages land.
  • Meta charges per delivered message. Messages from customers are free, and from October 1, 2026 each business number gets 1,000 free service messages a month.
  • The automations that pay off first for inbound leads are an instant first reply, a few qualifying questions, a handover to a person and one nudge before the 24-hour window closes.

The WhatsApp Cloud API is how software sends and receives WhatsApp messages for your business, with Meta running the servers. Nothing gets installed on your side. Your system, or a provider's, sends replies through Meta's Graph API and receives each customer message as a webhook: a small JSON notification pushed to an address you control. Since Meta retired the self-hosted On-Premises API in October 2025, the Cloud API is the only API route onto WhatsApp.

Connecting it takes five things: a Meta business portfolio, a WhatsApp account, an app with an access token, a business phone number and somewhere for incoming messages to land. Below you will find both ways to connect (through a provider or on your own), what Meta charges since its October 2026 pricing change, and the automations that matter most when the messages are new inquiries from people who want a price, a time or an answer.

What the WhatsApp Cloud API is, in plain terms

Meta calls the whole offering the WhatsApp Business Platform. The Cloud API is the part of it that does the messaging, and it has two halves:

  • Sending. Your software calls Meta's Graph API over HTTPS to send a message: plain text, a photo or document, an interactive message or an approved template.
  • Receiving. Meta pushes incoming messages, delivery status updates and errors to your webhook as JSON. Every message a customer sends arrives this way, which is what lets software answer it, route it or log it within seconds.

The Cloud API has no screen and no inbox. If people on your team are going to read and answer chats, they need software on top of it: something you build, or a provider's inbox. If you are still deciding whether you need the API at all compared with the free Business app, start with our guide to the WhatsApp Business API.

The names get mixed up constantly, so here is how they relate:

Name you will seeWhat it means
WhatsApp Business appThe free phone app for small businesses. People reply by hand.
WhatsApp Business PlatformMeta's official name for the API offering as a whole.
WhatsApp Business APIThe everyday name for the same platform.
WhatsApp Cloud APIThe messaging API on that platform, hosted by Meta.
On-Premises APIThe older self-hosted version. Expired in October 2025.

WhatsApp Cloud API vs On-Premise: the choice is already made

Older articles and some vendor pages still present "cloud or on-premise" as a decision. It no longer is. With the On-Premises API, a business or its provider ran the WhatsApp client on servers they managed themselves. According to Meta's sunset notice, it was wound down in steps:

  1. 2022: the Cloud API launches.
  2. January 9, 2024: from On-Premises version 2.53, new features ship only on the Cloud API, while the self-hosted client gets bug fixes and security patches only.
  3. July 1, 2024: business phone numbers can only be registered on the Cloud API.
  4. October 23, 2025: the final On-Premises version expires. Messages sent to or from numbers still registered on it are not delivered.

So if someone quotes you for hosting WhatsApp servers, the quote is out of date, and if an old integration stopped delivering in late 2025, its number has to move onto the Cloud API.

What you get by default on the Cloud API is the part that used to cost effort: Meta handles servers and updates, messages are encrypted in transit and at rest, and each business phone number can send up to 80 messages per second, with upgrades available. A service business will never come near that number.

What you need before you connect

Meta's overview lists the building blocks, and WhatsApp's Business Messaging Policy adds two that are easy to forget. Use this as a checklist before you start:

WhatWhy it mattersWho usually sets it up
Meta business portfolioEverything else is linked to it. If you run Facebook or Instagram ads, you probably have one.You
WhatsApp accountHolds your business phone numbers and profile.You, or created during signup
Messaging accountLinked to the portfolio and used for templates and billing.You, or created during signup
A business appThe app that holds the API access.Your developer, or the provider uses its own
Access token and permissionsLets software act for your account.Your developer or provider
Business phone numberReal or virtual. This is the number customers will message.You
Display nameThe business name shown on your profile.You
Payment methodNeeded once you go beyond free messages. Without one, service messages stop after the free monthly allowance.You
A place for webhooks to landYour own HTTPS endpoint or the provider's inbox. Without it, incoming messages go nowhere.Your developer or provider
Opt-in wordingYou may only message people who gave you permission to contact them on WhatsApp.You
A route to a personAutomation is allowed only with prompt, clear and direct escalation paths.You, in how you staff the inbox

How to get WhatsApp Cloud API: two ways to connect it

There are two routes, and the right one depends on whether you want to run software or just use it.

Setup through a provider

Most small teams connect through a provider whose software already has an inbox, automation and integrations. Providers use Meta's Embedded Signup, a guided flow that works on desktop and mobile. In it you:

  1. Log in with your Facebook or Meta business credentials.
  2. Accept the relevant terms of service.
  3. Select your business portfolio, or create one.
  4. Select a WhatsApp account, or create one.
  5. Enter your business phone number and verify it.
  6. Enter your display name.

Billing depends on the provider's arrangement with Meta. Some bill you through their own credit line with Meta; with others you add a payment method to your Messaging account yourself. Ask which one applies before you start, so service messages do not stop when the free allowance runs out.

Setup on your own

If you have a developer and want full control, Meta's get-started guide takes you from zero to a first message:

  1. Create the app. In the Meta App Dashboard, choose Create App, pick the use case "Connect with customers through WhatsApp" and select your business portfolio.
  2. Start using the API. In API Setup, connect a Messaging account. Meta automatically creates a test WhatsApp account and a test phone number with relaxed messaging limits, and the test number can send templates without a payment method on file.
  3. Send a first message. Generate a temporary access token, pick the test number as sender and your own phone as recipient, and send the hello_world template. Reply from your phone: that opens the 24-hour customer service window.
  4. Set up your webhook. Point Meta at an HTTPS endpoint you control, then reply in the chat again and confirm the JSON payload arrives.
  5. Replace the temporary token. It expires quickly. In Business Settings, add a system user, assign it your app and your WhatsApp account, and generate a token with the business_management, whatsapp_business_messaging and whatsapp_business_management permissions. Store it like a password.
  6. Add your real number with its display name and a payment method, and move off the test number.

One habit to build in from day one: treat every webhook event as something that might arrive twice, and make sure a repeat does no harm. A lead who gets the same greeting twice notices.

Is WhatsApp Cloud API free?

Meta's pricing is built around messages: it charges per message, and only when the message is delivered. For a business that mostly answers inbound inquiries, that works out like this:

  • Messages from customers are free. Meta does not charge for anything users send to businesses.
  • Your replies inside the window are mostly free. When a customer messages or calls you, a 24-hour customer service window opens, and it resets each time they write again. Replies inside it are service messages. From October 1, 2026, each business phone number gets 1,000 delivered service messages a month for free; charging starts at the 1,001st, and unused messages do not roll over.
  • Templates cost money. Marketing, utility and authentication templates are charged per delivered message. Utility templates sent inside an open window were free for a while, and Meta resumed charging for them on October 1, 2026.
  • Click-to-WhatsApp ads buy you time. If someone starts the chat from a click-to-WhatsApp ad in the Android or iOS app and you reply within the customer service window, a free entry point window opens for up to 7 days. While it is open, Meta does not charge for marketing, utility, authentication or service messages.
  • Provider fees are separate. If you connect through a provider, check what it adds on top of Meta's charges.

For example, if a clinic's number receives 200 new inquiries a month and the conversation averages four replies each, that is 800 service messages, inside the free 1,000. The costs that grow are templates, which you mostly need when you reply too late.

WhatsApp Cloud API features that matter when inquiries come in

The overview lists more than a lead-driven team will use. These are the features that decide whether inquiries turn into booked work:

  • Webhooks for every incoming message. Software sees a new inquiry the moment it arrives, at 7 a.m. or 11 p.m., so the first reply does not wait for someone to check a phone.
  • Interactive messages. Buttons and lists let a customer tap a choice instead of typing, which speeds up qualification on a phone screen: service type, preferred day, new or existing customer.
  • Rich media. Customers can send photos and documents. A roofer sees the damage, a car dealer sees the trade-in and a salon sees the reference picture before anyone calls.
  • Status updates. Your system learns whether a reply was delivered, so a failed send does not quietly leave a lead hanging.
  • Templates. The only way to restart a conversation once the window has closed, and they need approval in advance.
  • Messaging limits that spare inbound replies. Meta caps how many unique people you can message outside a customer service window in a rolling 24 hours, set per business portfolio. Replies to people who just wrote to you are inside the window, so answering inquiries does not eat into that cap.

Lead-response automations worth building first

Connecting the API is the technical step; the result comes from the first hour of each conversation. These are the automations that pay off soonest, with the rule each one has to respect:

When this happensAutomate thisRule to respect
A new message arrives, any hourAn instant first reply that answers what was asked and asks one questionAutomation is allowed inside the 24-hour window if a person is reachable
The lead answersTwo or three qualifying questions: what, where, when, roughly what budgetNever ask for full card or bank account numbers in the chat
The lead is qualifiedOffer two or three times as buttons and book a call or visitStay inside the window, or use an approved template
The lead asks for a person, complains or has a complicated caseHand the chat to a named person on the teamThe policy requires prompt, clear and direct escalation paths
The lead goes quietOne short nudge while the window is still openAfter the window closes, only approved templates
The window has closedAn approved template asking whether to keep the inquiry openYou need opt-in, and every opt-out must be respected

A first reply that works across most service businesses has three parts: refer to what the person asked, ask one question and offer a next step. For example: "Hi [first name], thanks for your message about [service]. To point you in the right direction, is this for a specific date or are you still comparing options? We have consultation slots on [day] and [day]." A real estate office would ask about area and budget, an insurance broker about what needs cover.

Set the handover rules before you switch automation on, not after the first complaint. For the timing of nudges when a lead stops answering, see our guide to lead follow-up automation. If you also take inquiries through Messenger, the same first-reply logic applies there, covered in our guide to Facebook Messenger for business.

WhatsApp is rarely the only door inquiries come through, and a lead from a form deserves the same first minute as a lead in a chat. Tools such as Konverto pick up leads from Facebook and Instagram lead ads, website forms and website chat, reply by SMS and email typically within a minute in your own tone, ask the qualifying questions you choose and book a call or visit straight into your calendar. Konverto also hands the conversation to a person when a lead asks for one or a call-back, or raises a complaint, and push new leads to HubSpot and Pipedrive once connected, and create Salesforce opportunities once its package is installed in your Salesforce org.

Before you go live on any channel, run one test from a personal phone: send an inquiry at a time nobody is working and see what happens. If the answer arrives within a minute, is useful and offers a next step, the setup is doing its job.

Frequently asked questions

Is WhatsApp Cloud API free?

Meta charges per delivered message. Messages customers send you are free, each business phone number gets 1,000 free service messages a month from October 1, 2026, and template messages are charged per delivered message. A test number can send templates without a payment method on file.

What is the difference between WhatsApp Cloud API and WhatsApp Business API?

WhatsApp Business API is the everyday name for Meta's WhatsApp Business Platform. The Cloud API is the part of that platform software uses to send and receive messages, and since the On-Premises API expired in October 2025 it is the only API version still delivering messages.

Can I still use the WhatsApp On-Premises API?

No. New phone numbers could only be registered on the Cloud API from July 1, 2024, and the final On-Premises version expired on October 23, 2025. Messages sent to or from numbers still registered on the On-Premises API are not delivered.

Do I need a developer to connect WhatsApp Cloud API?

Only if you build the connection yourself, which means creating a Meta app, generating a system user access token and running a webhook endpoint. Through a provider's signup flow you log in with your Facebook or Meta business account, choose your business portfolio, verify your number and enter a display name.

Can I automate replies with WhatsApp Cloud API?

Yes. WhatsApp's Business Messaging Policy allows automation when you respond during the 24-hour window, as long as you offer prompt, clear and direct ways to reach a person, such as a transfer to a human in the chat. Outside the window you can only send approved message templates.

Sources

Want every enquiry answered within a few minutes?