API Reseller
WhatsApp API
WhatsApp Business messaging with template approval handled, session management, and delivery and read receipts. Billed per conversation by the platform, which is worth modelling before switching notification volume onto it.
What you get
- Template submission and approval management
- Session and conversation window handling
- Delivery and read receipts
- Media messages: documents, images and PDFs
- Per-conversation usage reporting
The contract
- Auth
- Issued credentials per key pair, over TLS. Signed requests where the rail requires it.
- Templates
- Meta-approved template required to open a conversation.
- Session
- A user reply opens a 24-hour window in which free-form messages are allowed.
- Delivery
- Asynchronous, with sent/delivered/read receipts by webhook.
- Environments
- Sandbox mirrors production semantics, including failures.
FAQ
About whatsapp api
Why can I not send free-form messages to any number?
Meta only allows an approved template to open a conversation. Once the user replies, a 24-hour window opens in which free-form messages are allowed; after it closes you are back to templates. This is Meta's rule, not ours.
How is this billed?
Per conversation by Meta, not per message, so a 24-hour window costs the same whether it carries one message or twenty. That makes batching related messages into an open window materially cheaper than spreading them out.