The WhatsApp Cloud API is the interface Meta provides for software to send and receive WhatsApp messages, and to make and receive calls, on a business phone number. A chatbot, a team inbox or an AI agent that talks to customers on WhatsApp is almost always calling the Cloud API underneath. You can call it yourself with a few requests, or connect a platform that calls it for you.
This guide explains what the Cloud API does, walks through the setup steps Meta documents, covers cost and limits, and says when building directly stops making sense. Every technical detail comes from Meta's developer documentation.
What the Cloud API includes
Meta's WhatsApp Business Platform has several interfaces. The Cloud API covers three jobs: messaging, which sends text, media and interactive messages; calling, which makes and receives calls to customers; and groups, which creates and manages group conversations. Beside it sit the Business Management API, for accounts, templates and analytics, and the Marketing Messages API for optimised marketing sends.
The Cloud API is built on Meta's Graph API and runs over HTTP. You send a request to an endpoint named for your phone number's ID, with an access token in the header. The reverse direction runs on webhooks: when a customer writes to you, Meta posts a JSON payload to a URL you provide, and every delivery status, such as sent, delivered and read, arrives the same way.
The two rules that shape every message
You can send a template message to a customer at any time. A template is a message whose text Meta has approved in advance, in one of three categories: marketing, utility or authentication.
You can send any other message, such as plain text, an image or a button list, only inside the customer service window. That window opens when a customer messages you and lasts 24 hours, resetting each time they write again. If the window has closed and you have nothing approved to send, the message will not go. Our 24-hour rule guide covers the details.
Getting started in six steps
This is the path that Meta's get-started guide for the Cloud API sets out.
Register as a Meta developer with a Facebook account.
Create a Meta app in the App Dashboard and choose the use case "Connect with customers through WhatsApp". Select or create a business portfolio.
Open the API Setup page, connect the app to a Messaging account, and note its ID. If you created a new business portfolio, Meta may have created the account for you.
Generate a temporary access token, pick the test sender number, add your own number as the recipient and send the sample message. It uses a template called hello_world. Reply from your phone so a customer service window opens.
Set up a webhook endpoint. Meta provides a sample server for tests. Reply in the chat and you will see the incoming payload, which carries the customer's number and message text.
Create a system user in Business Settings, assign it your app and your WhatsApp account, and generate a permanent token with three permissions: business_management, whatsapp_business_messaging and whatsapp_business_management. The temporary token expires quickly and is not suitable for real use.
A first message looks like this in Meta's own examples:
POST https://graph.facebook.com/<API_VERSION>/<PHONE_NUMBER_ID>/messages
Authorization: Bearer <ACCESS_TOKEN>
{ "messaging_product": "whatsapp",
"to": "<CUSTOMER_NUMBER>",
"type": "template",
"template": { "name": "hello_world", "language": { "code": "en_US" } } }
Once the test works, you add a real business phone number, which must receive a verification code by text message or call, then create your own templates for review. Meta's template documentation says review can take up to 24 hours.
What you still have to build
The Cloud API moves messages. It gives you no inbox, no assignment, no contact list and no chatbot. If you call it directly, your team writes or buys each of these:
A webhook receiver that checks Meta's request signature, acknowledges quickly and handles repeated deliveries of the same message.
A store for conversations, contacts and message statuses.
A screen where several agents read and reply, with notes and assignment.
A template manager, since each template needs approval and may be paused.
Logic for the 24-hour window, so the right message type goes at the right time.
Any automation or AI that answers customers, and the hand-off to a person.
That is a sensible project for a software company that wants WhatsApp inside its own product. For most service and sales teams it is a long build to arrive at what a platform already offers.
Cost
Meta charges nothing for access to the Cloud API itself. It charges per delivered message, only for messages from the business, by category and by the customer's country. As of its 1 October 2026 card, a marketing message to a US or Canadian number is US$0.0250 and a utility message US$0.0034, and to a Singapore number US$0.0732 and US$0.0160. Each business phone number gets 1,000 free service messages a month. Meta may change rates on the first day of a quarter. See our pricing guide for worked monthly bills.
Limits to plan for
Messaging limits. A new business portfolio can start conversations with 250 unique customers a day outside the 24-hour window. Verification or high-quality sending raises it to 2,000, and it then rises automatically to 10,000, 100,000 and unlimited. See our guide to messaging limits.
Throughput. A number that runs on both the Cloud API and the WhatsApp Business app has a fixed 20 messages per second.
Quality. Meta rates each number from customer feedback, and a poor rating can lower your limits.
Direct, or through a platform
Meta also lets software companies onboard other businesses, as a Tech Provider or a Solution Partner, through a sign-up flow called Embedded Signup. A customer signs in with Facebook, verifies the number and grants the provider access to their WhatsApp account, and the provider's software handles everything above. This is how a business with no developers gets on the Cloud API in a short run of screens.
| Call the Cloud API yourself | Use a platform | |
|---|---|---|
| Who builds the inbox | Your engineers | The platform |
| Time to first customer reply | As long as your build takes | The time to connect a number |
| Meta's message fees | Billed to your account | Billed to your account or marked up, depending on the provider |
| Customisation | Unlimited, at your cost | Limited to what the platform offers |
| Suits | Software products with WhatsApp inside | Support, sales and booking teams |
How to do this in Volty
Volty connects your number to the WhatsApp Business Platform through Meta's Embedded Signup, from inside Volty and with no code, and the conversations land in a shared inbox with an AI agent that answers from your website and files. A number already live on the WhatsApp Business app can stay there through coexistence, and Volty can import up to six months of one-to-one chat history if you agree to share it. Meta bills you for messages directly. Start on the WhatsApp AI page, check pricing, and try it on a 7-day free trial.
Frequently asked questions
What is the WhatsApp Cloud API?
The WhatsApp Cloud API is the part of Meta's WhatsApp Business Platform that lets software send and receive WhatsApp messages and calls for a business phone number. It is the API most inboxes, chatbots and AI agents use to reach WhatsApp.
Is the WhatsApp Cloud API free?
The API itself has no subscription from Meta. You pay Meta per delivered message, by category and country, with 1,000 free service messages a month on each business phone number. Any inbox or chatbot software you add has its own fee.
Do I need to code to use the WhatsApp Cloud API?
To use it directly, yes. You create a Meta app, call the messages endpoint, and run a webhook server to receive replies. To avoid code, connect your number to a platform that has already built the inbox.
What do I need to start with the Cloud API?
A Facebook account, a Meta app with the WhatsApp use case, a business portfolio, a phone number that can receive a verification code, and a server that can receive webhooks. For live use you also need a payment method and a permanent access token from a system user.
Can I use the Cloud API and the WhatsApp Business app on one number?
Yes, through coexistence, in countries where Meta offers it. Numbers that run on both have a fixed throughput of 20 messages per second, and some app features, such as broadcast lists, are switched off.










