WhatsApp API Integration That Connects the Cloud API to Your App, CRM and Website
Wire WhatsApp into the tools your business already runs. WaBulkSend sits on top of the official WhatsApp Cloud API: connect your own number, trigger template sends from your CRM, store, or app through our REST API, and receive replies and delivery events on your own webhook. Or build straight against Meta's raw endpoints if you prefer.
The demo gives you 25 messages on your own number, one time. No card required.
Send a message
One POSTPOST /{phone_number_id}/messages
Authorization: Bearer {token}
{
"messaging_product": "whatsapp",
"to": "15551234567",
"type": "template",
"template": { "name": "order_update" }
}
The short answer: WhatsApp API integration means connecting the official WhatsApp Cloud API to your own software so you can send and receive WhatsApp messages programmatically. You send a message with a single HTTP POST to the /messages endpoint using your phone number ID and an access token, and you receive inbound messages and delivery statuses as JSON on a webhook URL you host over HTTPS. The Cloud API replaced the On-Premises API, which Meta retired in October 2025, so every new integration runs on the cloud version. WaBulkSend layers bulk campaigns, a REST API, and signed outbound webhooks on top, so your CRM, store, or app can trigger template sends and receive replies and statuses without you building the sending, template, and reporting layer yourself.
What WhatsApp API integration actually involves
At its core the WhatsApp Cloud API is a REST API. You authenticate with an access token, you send messages by posting JSON to an endpoint tied to your business phone number ID, and you find out what happened by listening on a webhook. That is the whole shape of it. The complexity is not in the requests, it is in the account setup around them: verifying your business in Meta Business Manager, registering and verifying the phone number, getting templates approved, and hosting a public HTTPS webhook with a valid certificate.
There are two ways to integrate. The direct route is to build against Meta's Cloud API yourself, which gives you full control and is a good fit for engineering teams that want the raw developer API. The faster route is to integrate through WaBulkSend. You connect your own WhatsApp Business number once by pasting its phone number ID, WABA ID, and access token, and WaBulkSend handles template sync and submission, sending and pacing, Meta's webhook, and delivery reporting, with a REST API for your systems and a dashboard your non-technical team can use. Business verification and number registration stay with you and Meta.
Most businesses want the same handful of things: send order and appointment updates from their backend, sync inbound replies into a CRM, and let support answer from a shared inbox. All of that comes down to sending messages one way and receiving webhooks the other. WaBulkSend covers the sending side and forwards every inbound reply to your webhook; it has no chat inbox, so answering customers one to one needs your CRM, help desk, or another tool. Below is how each piece fits, with the setup steps, the send request, and the rules that apply to US numbers in 2026.
How to integrate the WhatsApp API
Six steps from a fresh account to a working two-way integration.
Verify the business and number
Verify your business in Meta Business Manager, then add and verify the phone number you will send from with a code by call or SMS. Set the display name and profile.
Get your credentials
Grab the phone number ID and a permanent access token with messaging scope. These two values authenticate every request you make.
Send your first message
POST JSON to the /messages endpoint. Free-form text works inside the 24-hour window; outside it you send an approved template.
Set up the webhook
Point your public HTTPS endpoint at WhatsApp so inbound messages and delivery statuses arrive as JSON. A valid SSL certificate is required.
Connect your CRM or store
Map events both ways: your backend fires outbound messages, and inbound replies flow into your CRM, help desk, or shared inbox.
Go live and monitor
Move from the test number to production, watch delivery and quality rating, and scale volume as your number tier increases.
What you can integrate WhatsApp with
The same two building blocks, sending messages and receiving webhooks, cover almost every integration a business needs.
| Integration | What it does |
|---|---|
| Website chat and forms | Start a WhatsApp conversation from a chat widget or lead form, so a website visitor becomes a chat you can answer. |
| CRM and sales tools | Send outbound updates from the CRM and sync every inbound reply back to the contact record for a full history. |
| Ecommerce store | Fire order confirmations, shipping updates, and cart reminders from Shopify or WooCommerce events. |
| Help desk and shared inbox | Route inbound messages to agents and let a team answer one number together. |
| Backend and internal apps | Trigger authentication codes, alerts, and notifications straight from your own services. |
| Automation platforms | Connect through webhooks or tools like Zapier and n8n to move data between apps without custom code. |
Prefer the code path? Read the step-by-step guide to send a WhatsApp message with the API, or see how to send login codes with the WhatsApp OTP API.
What WaBulkSend adds on top of the API
The parts of an integration you would otherwise build and maintain yourself.
Connect your own number
Paste your phone number ID, WABA ID, and access token once. Business verification and number registration stay in your own Meta account, so the number and its history remain yours.
Template management
Create, submit, and track template approvals in a dashboard instead of raw API calls, with categories set correctly.
Webhook handling
WaBulkSend receives Meta's webhook and forwards signed, normalized events (inbound messages, delivery statuses, failures, opt-outs, template status) to your endpoint.
REST API for your systems
Your CRM, store, Zapier, Make, or n8n can create contacts and send a template campaign to a segment, a tag, or a list of numbers. There are no one-click connectors; you wire it up with the API and webhooks.
Consent and opt-outs
Campaigns only go to opted-in contacts, and a STOP reply or a tap on Meta's Stop promotions button opts the contact out automatically.
Delivery analytics
See sent, delivered, read, and reply rates per campaign, with your number quality rating on the number page.
Cloud API vs the retired On-Premises API
If you are integrating in 2026, you use the Cloud API. Here is why the choice is already made.
| Factor | Cloud API | On-Premises API |
|---|---|---|
| Hosting | Hosted by Meta, no servers | You host and maintain it |
| Status in 2026 | The only supported option | Retired in October 2025 |
| Setup speed | Fast, minutes to hours | Slow, needs infrastructure |
| Updates | Automatic | Manual upgrades |
| Cost to call | Free to call, pay Meta per delivered template | Same per-message billing |
Calling the API is free; you pay Meta per delivered template message. See what is billed and what is free on WhatsApp Business API pricing.
The rules your integration has to respect for US numbers
Two rules shape every WhatsApp API integration. First, the 24-hour customer service window: once a customer messages you, you can send free-form messages for 24 hours. Outside that window, you must send a pre-approved message template. Your integration needs to know which side of that window it is on, so it sends free-form when it can and a template when it cannot.
Second, message categories and the US pause. Templates fall into utility, authentication, and marketing categories. Meta paused marketing-category templates to US phone numbers in April 2025, and that pause holds in 2026. So an integration serving US customers should lean on utility and authentication templates, order updates, appointment reminders, one-time codes, and on free-window replies, rather than trying to push marketing templates that will be blocked.
Handle those two rules correctly and the rest is straightforward engineering. Send the right message type at the right time, keep your webhook healthy, and watch your number quality rating. For the wider picture of how the API works and how to get access, read our WhatsApp Business API guide.
WhatsApp API integration, answered
How do I integrate the WhatsApp API?
Verify your business in Meta Business Manager, register and verify a phone number, and get a phone number ID plus an access token. Then send messages by posting JSON to the /messages endpoint and receive inbound messages on a public HTTPS webhook. WaBulkSend does not do that Meta setup for you. Once your number exists, you connect it with its phone number ID and access token, and WaBulkSend gives you campaigns, a REST API your CRM, store, or app can call, and signed webhooks for replies and statuses.
Can I integrate WhatsApp into my website?
Yes. You can add a WhatsApp chat button or a lead form that opens a conversation, then handle the messages through the WhatsApp Cloud API. Inbound messages arrive on your webhook and you reply through the API. WaBulkSend does not include a website widget or a chat inbox. For a simple click-to-chat button, our free WhatsApp link generator makes a wa.me link and QR code you can place on your site.
Is there a WhatsApp developer API?
Yes. The WhatsApp Cloud API is Meta's official developer API, a REST interface you call over HTTPS with JSON. It replaced the older On-Premises API, which Meta retired in October 2025. You can build directly against it, or integrate through WaBulkSend to skip building the template, sending, and reporting layer. You still set up your own Meta account and number.
Can I connect the WhatsApp API to my CRM?
Yes. A CRM integration is bidirectional: your CRM sends outbound messages like order confirmations through the API, and inbound replies flow back over webhooks into the contact record. That gives you one view of every WhatsApp conversation alongside email and calls. WaBulkSend has no prebuilt CRM connectors: your CRM calls our REST API to send, and our signed webhooks deliver replies and status events to an endpoint you, Zapier, Make, or n8n control.
Does the WhatsApp API cost money?
The Cloud API is free to call. Since July 1, 2025 Meta charges per message, and only when a template message is delivered, at a rate set by the template category and the recipient country. Meta publishes those rates in a downloadable rate card rather than in its docs. Non-template replies inside the 24-hour window are free for the first 1,000 per business number each month and billed at the utility rate after that, since October 1, 2026. WaBulkSend adds a plan on top, from $49 a month or $24.50 a month billed yearly, after a one-time demo of 25 messages. Meta bills its fees to your own WhatsApp Business Account.
What is a webhook in the WhatsApp API?
A webhook is a URL on your server that WhatsApp calls with a JSON payload whenever something happens: a customer sends you a message, or an outbound message changes delivery status. You host it over HTTPS with a valid SSL certificate. Webhooks are how your integration receives everything coming back from WhatsApp in real time.
How long does WhatsApp API integration take?
A direct Cloud API integration can send a test message in an hour, but business verification and template approval can take a few days. WaBulkSend does not speed up Meta's checks, but once your number is approved, connecting it and sending a first campaign takes minutes instead of a development sprint. The exact timing depends on how fast Meta verifies your business and number.
Integrate WhatsApp without building the sending layer
Connect your own Cloud API number, trigger template sends from your CRM, store, or app through our API, and get replies on your webhook. The demo gives you 25 messages on your own number, one time, no card required.
Start sending