Provider Guide
Webhook standard event differences
Standard events mapped by the current provider parsers and their payload differences. This is source-level support, not a guarantee that every account or deployment emits every mapped event.
Capability
| Capability | Telegram | X | LINE | Zalo | TikTok | |
|---|---|---|---|---|---|---|
| message.received | Full | Full | Full | Full | Full | Full |
| message.updated | Full | Full | Not supported | Full | Not supported | Not supported |
| message.deleted | Full | Full | Not supported | Full | Not supported | Not supported |
| message.read | Full | Partial | Not supported | Full | Not supported | Not supported |
| message.reaction | Full | Full | Not supported | Full | Not supported | Not supported |
| message.delivered | Full | Partial | Not supported | Full | Not supported | Not supported |
| conversation.updated | Full | Full | Not supported | Not supported | Not supported | Not supported |
| conversation.deleted | Not supported | Full | Not supported | Not supported | Not supported | Not supported |
| conversation.cleared | Not supported | Full | Not supported | Not supported | Not supported | Not supported |
| conversation.history | Not supported | Full | Not supported | Not supported | Not supported | Not supported |
| group.updated | Full | Full | Not supported | Not supported | Not supported | Not supported |
| group.join_request | Not supported | Full | Not supported | Not supported | Not supported | Not supported |
| account.status.updated | Full | Full | Full | Full | Full | Full |
| account.started | Not supported | Full | Not supported | Not supported | Not supported | Not supported |
| account.history.synced | Not supported | Full | Not supported | Not supported | Not supported | Not supported |
| account.auth.required | Full | Full | Not supported | Full | Full | Full |
| account.auth.succeeded | Full | Full | Full | Full | Full | Full |
| account.auth.failed | Full | Full | Full | Full | Not supported | Not supported |
Notes
- For WhatsApp, delivery receipts map to message.delivered and read receipts map to message.read; sent and failed are not separate standard events. Group chat receipts can be filtered to keep webhook volume manageable.
- WhatsApp reactions are surfaced as message.reaction events (the reaction emoji is on data.event.reaction; the original message id is under data.message.target_message_id).
- Telegram message.received payloads may include edit_message_id when an existing message was edited rather than newly sent.
- X does not deliver real-time read receipts; status updates are limited to sent and failed.
- Zalo status events are best-effort and may be delayed or omitted under low-traffic conditions.
- Current source mapping emits message.received only for private conversations. Group, acknowledgement, notice, and comment events are not public standard events, and source support is not a real-account E2E guarantee.