Webhooks
Webhooks let your own systems (a website, store, or ERP) trigger Whatsaper actions and react to events.
Trigger webhook (Whatsaper receives)
Register a webhook in the Whatsaper app, map the incoming payload fields to a WhatsApp template, and you get a unique token. Your system then calls:
curl -X POST https://api.whatsaper.com/api/ecommerce-webhook/trigger/YOUR_WEBHOOK_TOKEN \
-H "Content-Type: application/json" \
-d '{ "customer": { "phone": "+201234567890" }, "order_id": "ORD-42" }'Whatsaper maps the payload using the webhook’s field mapping, renders the mapped template, and sends the WhatsApp message. Requires a plan that includes the WhatsApp webhook feature.
Manage webhooks
These endpoints are authenticated with your API key:
| Method | Path | Purpose |
|---|---|---|
POST | /api/ecommerce-webhook/create | Create a webhook |
GET | /api/ecommerce-webhook/list | List webhooks |
GET | /api/ecommerce-webhook/:id | Get one webhook |
PUT | /api/ecommerce-webhook/:id | Update a webhook |
DELETE | /api/ecommerce-webhook/:id | Delete a webhook |
PATCH | /api/ecommerce-webhook/:id/toggle | Enable or disable |
POST | /api/ecommerce-webhook/:id/map-template | Map payload fields to a template |
GET | /api/ecommerce-webhook/:id/stats | Delivery stats |
GET | /api/ecommerce-webhook/:id/trigger-logs | Recent triggers |
GET | /api/ecommerce-webhook/:id/message-logs | Messages sent from this webhook |
PUT | /api/ecommerce-webhook/:id/merchant-notifications | Merchant notification settings |
Channel receivers
Whatsaper also exposes provider webhook receivers that Meta and messaging providers call directly — these are configured in the app, not called by you:
GET|POST /api/webhook/facebookGET|POST /api/webhook/instagramPOST /api/webhook/telegram/:workspace_id
Outbound events
Pushing Whatsaper events (new message, delivery status) out to your systems is not available yet. The trigger webhook above is inbound only.