When should I use Meta-compatible messaging?
Use it when your application already builds Meta WhatsApp Cloud API payloads and you want Whats91 to handle authentication, routing, billing, and reporting.
Understand the Meta-compatible JSON message sending endpoints exposed through Whats91.
Messaging Meta-Compatibility Overview
Summary
Use Meta-compatible messaging endpoints when your integration already produces WhatsApp Cloud API style payloads and needs Whats91 handling.
Prerequisites
- Bearer token authentication
- A Meta-compatible WhatsApp message body
The Messaging Meta-Compatibility section documents Meta WhatsApp Cloud API-style JSON payloads accepted by Whats91. Use these endpoints when your integration already builds Meta-style message bodies and needs Whats91 authentication, sender resolution, billing guard, blacklist guard, report logging, reconnect queue, and conversation logging.
| Method and path | Purpose |
|---|---|
| POST /api/v2/messages | Send a Meta-compatible payload. Sender resolves from token/default or senderId. |
| POST /api/v2/{phoneNumberId}/messages | Send through the sender phoneNumberId selected by the URL path. |
Content type is application/json only. Supported Meta payload types are text, image, video, audio, document, sticker, location, contacts, template, interactive, and reaction.
Every Meta-compatible body should include messaging_product: whatsapp, the recipient to, and either an explicit type with its matching object or an omitted type that defaults to text.
- Authorization: Bearer w91_live_xxx is required unless auth is supplied in the JSON token fields.
- to is required for every send request.
- type defaults to text when omitted.
- If type is supplied, the matching object is required; for example text for type text or template for type template.
- senderId can be sent in the body for POST /api/v2/messages.
- senderId is ignored when POST /api/v2/{phoneNumberId}/messages selects the sender by path.
Frequently Asked Questions
Does Whats91 change the Meta payload shape?
The endpoint keeps the Meta-compatible request style while adding Whats91 processing and response metadata where needed.
Can I use phoneNumberId in the URL?
Yes. Meta-compatible routes include variants that select the sender by phoneNumberId.
Related Documentation
Messaging
Understand the Whats91-specific message sending endpoints for templates, chat messages, media, buttons, and lists.
Template
Send Meta-compatible template messages with language and components objects.
Examples
Practical webhook receiver examples and use cases for CRM, delivery tracking, and template operations.