A REST API that gives you Meta’s message ID, not an abstraction over it
If you are wiring WhatsApp into your own product, you need the real identifiers and the real status events. Both are exposed rather than hidden behind a simplified wrapper.
Included in the platform licence. Not a paid add-on.
How do you integrate the WhatsApp Business API?
The WhatsApp API lets your own systems send and track messages programmatically. WappBlaster exposes a REST send-message API that returns Meta’s own WhatsApp message ID, a configurable webhook URL that receives delivery, read and failure statuses from Meta, custom reference IDs echoed back in webhook payloads, a file upload API for media, and inbound webhook triggers that start bot flows or automations.
Trusted by 3,500+ businesses
- 4.8 / 5
-
-
-
-
- Meta Tech Provider
- D-U-N-S Registered
Some of the businesses using WappBlaster products every day
Capabilities
What you get
Everything here is documented and shipping today, not on a roadmap.
REST send-message API
Send from your own backend, documented with a Postman walkthrough for the official number.
Direct Meta message IDs
The send response carries Meta’s WhatsApp message ID, which is what you need to reconcile against Meta’s own reporting.
Status webhooks
Set a webhook URL and receive delivery reports and message statuses from Meta as they happen.
Custom reference IDs
Send your own reference with the message and get it back in the webhook, so no lookup table is needed.
File upload API
Upload media programmatically for use in messages and templates.
Inbound webhook triggers
A URL your systems can call to start a bot flow or an automation, which is the simplest integration path of all.
How it works
Setting it up
- 1
Get your credentials
API access against the WhatsApp channel you registered.
- 2
Send a test with Postman
Documented step by step against your own number.
- 3
Point the status webhook at your stack
Delivery and read events flow in immediately.
- 4
Add reference IDs
So every event maps to an order, ticket or user in your system.
Where it earns its keep
Common uses
-
Transactional notifications
Your app sends order and account updates directly.
-
OTP delivery
Authentication templates fired from your auth service.
-
Internal alerting
Systems paging a team over WhatsApp instead of email.
-
Custom CRM integration
Where an off-the-shelf connector does not fit.
-
Data warehouse reporting
Raw delivery events into your own analytics.
-
SaaS products embedding WhatsApp
Sending on behalf of their own customers.
Ships in these products
Frequently asked questions
Straight answers about WhatsApp business API integration.
Is there a REST API for sending WhatsApp messages?
Yes. You can send messages for your official WhatsApp number over REST, and the documentation includes a Postman walkthrough. The response includes Meta’s own WhatsApp message ID.
Link to this answerHow do I receive delivery reports in my own system?
Set a webhook URL on the channel and Meta’s status events (sent, delivered, read, failed) are forwarded to it as they occur.
Link to this answerCan I attach my own ID to a message?
Yes. Send a custom reference ID with the API call and it comes back in the webhook payload, so events map to your records without a separate lookup.
Link to this answerDo I need a developer to use WappBlaster?
No. Everything in the platform works without code. The API is there for teams that want to drive WhatsApp from their own product, not a prerequisite for using it.
Link to this answerStill not answered?
Ask a real person. We reply on WhatsApp, usually within the hour.
Platform and setup
Related features
Same licence, same login. These work together out of the box.
See API and webhooks on your own account
A short call on your real list and your real templates. No card, no sandbox.
- Set up with you on a call, not a help article
- Official Meta WhatsApp Business Platform
- Flat annual fee, Meta charges passed through at cost