Thank you, Biden. Unfortunately, we don't use WhatsApp-specific callbacks, but we activated the triggers: MESSAGE_DELIVERY, MESSAGE_INBOUND, CONVERSATION_START // for the Conversation API WHATSAPP_TEMPLATE_APPROVED, WHATSAPP_TEMPLATE_REJECTED // for the Provisioning API As Sam said we can easily detect the event type between a WHATSAPP_TEMPLATE_APPROVED and WHATSAPP_TEMPLATE_REJECTED event because they have a top-level structure in common. However, it's very difficult to distinguish a MESSAGE_DELIVERY event from a MESSAGE_INBOUND or a WHATSAPP_TEMPLATE_XXX event based on the payload because they have nothing in common. I understand that these are very core functions, and my intention is to offer a suggestion for future improvement. For example, adding another custom header to the request like: x-sinch-webhook-trigger=<trigger_type> //ie: MESSAGE_DELIVERY could be a great help for detection and it shouldn't affect backward compatibility. Thank you Have a nice day! Diana
... View more
