A bulk message sender API is how WhatsApp stops being a tool someone clicks and becomes part of the system: an order confirms itself, a renewal reminds itself, a lead gets its catalogue the moment it arrives. Here is what the API actually is on Meta’s platform, what it returns, and what it costs.
What the API is, and is not
- It is Meta’s WhatsApp Business Platform, reached through a provider’s REST layer: templates, contacts, media, sends, and webhooks for everything that happens afterwards.
- It is not an API to the WhatsApp Business app or to WhatsApp Web. Anything marketed as that is a scraper, and it carries the ban risk of every unofficial tool.
What you call
Send template
Template name, recipient number, variable values, optional header media and button payloads. Returns a message id.
Contacts
Create, update and tag contacts; set consent source and date; read a contact’s event history.
Templates
List approved templates and their variables; submit new ones for Meta review.
Media
Upload an image, video or PDF once and reference it by id in sends.
Campaign
Send one template to a segment or a list of recipients in one call; the platform paces it within your tier.
Webhooks
Register an endpoint; receive signed events for every message and reply.
A send, in practice
POST /messages/template
The response is a message id. Everything after that arrives on the webhook.
What comes back
Webhook payload
- sent, delivered, read, failed per message, with the failure reason when there is one.
- inbound messages and button clicks, with the contact’s tags attached.
- Signed, so your endpoint can verify the source. Retried if your endpoint is down.
Full event reference in how WhatsApp API webhooks work.
Rate limits and tiers
The Cloud API itself is fast. The binding constraint is the number’s messaging tier: 1,000 unique recipients in 24 hours for a new number, rising to 10,000, 100,000 and unlimited as the number sends with a healthy quality rating. The platform queues a large campaign and paces it inside the tier so your code does not have to. Blocks and reports are what lower the tier, so the API is only as scalable as the consent behind the list. Details in WhatsApp API rate limits explained.
Patterns that work
- Transactional from the backend: order, shipment, payment, renewal events fire utility templates directly.
- Marketing from the dashboard: segments, scheduling and A/B live there; the API reads the results.
- CRM as source of truth: Zoho, HubSpot or Salesforce hold the contact; WhatsApp events flow into the timeline via native sync or your webhook consumer.
- Store events: Shopify and WooCommerce are connected natively; abandoned carts become a segment without code.
What it costs
- Platform, including the API: ₹7,999 a year in India, $200 elsewhere. Unlimited API calls, unlimited contacts. No developer plan, no per-call fee.
- Meta’s per-message charge: per message by country and category, passed through at cost. Service replies inside the 24-hour window are free today and become billable from 1 October 2026 (details).
Next step
The WhatsApp Marketing API page covers the developer surface; the Bulk WhatsApp Sender Software page covers the dashboard side of the same licence. Keys are issued on the free trial call. Language-specific guides: Shopify, Zoho CRM, HubSpot.