Skip to Content
Webhooks

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:

MethodPathPurpose
POST/api/ecommerce-webhook/createCreate a webhook
GET/api/ecommerce-webhook/listList webhooks
GET/api/ecommerce-webhook/:idGet one webhook
PUT/api/ecommerce-webhook/:idUpdate a webhook
DELETE/api/ecommerce-webhook/:idDelete a webhook
PATCH/api/ecommerce-webhook/:id/toggleEnable or disable
POST/api/ecommerce-webhook/:id/map-templateMap payload fields to a template
GET/api/ecommerce-webhook/:id/statsDelivery stats
GET/api/ecommerce-webhook/:id/trigger-logsRecent triggers
GET/api/ecommerce-webhook/:id/message-logsMessages sent from this webhook
PUT/api/ecommerce-webhook/:id/merchant-notificationsMerchant 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/facebook
  • GET|POST /api/webhook/instagram
  • POST /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.

Last updated on