WhatsApp webhooks
Set a webhook URL on each device and QuackAPI will POST JSON to it when something happens.
Events
| Event | When |
|---|---|
| message.received | A message arrives on the device |
| message.sent | A queued message was handed to WhatsApp |
| message.failed | A message could not be sent |
| message.unknown | The result could not be confirmed |
Logs
Every webhook attempt is listed on the device page, so you can see what was sent and what your server answered.
What people build with them
- Support inbox: save every message.received into a helpdesk or CRM and reply from there.
- Delivery tracking: mark an order message as sent or failed from message.sent and message.failed.
- Auto-replies and menus: answer a keyword such as STATUS with the order state.
- Alerts: tell your team when a customer writes outside office hours.
How a message moves through the events
You send with the REST API and get a queued response. When WhatsApp accepts it you get message.sent. If it cannot be sent you get message.failed with a reason. If the final state cannot be confirmed you get message.unknown, so treat that one as not delivered until you check.
Good practice
- Return a 2xx within a few seconds and process in the background.
- Use messageId to ignore a repeated delivery.
- Keep the URL secret. Webhooks are not signed today.
- Use the webhook log on the device page to see exactly what was sent and how your server answered.
Related
Last reviewed 2026-11-09. QuackAPI is an unofficial linked-device service. Acceptable use