Skip to content

Latest commit

 

History

History
32 lines (20 loc) · 2.18 KB

File metadata and controls

32 lines (20 loc) · 2.18 KB

WebhookPayloadMessageMetadata

Interactive message metadata (present when message is a quick reply tap, postback button tap, or inline keyboard callback)

Properties

Name Type Description Notes
quickReplyPayload String Payload from a quick reply tap (Facebook/Instagram Messenger). [optional]
postbackPayload String Payload from a postback button tap (Facebook/Instagram Messenger). [optional]
postbackTitle String Title of the tapped postback button (Facebook/Instagram Messenger). [optional]
callbackData String Callback data from an inline keyboard button tap (Telegram). [optional]
interactiveType InteractiveTypeEnum WhatsApp only. Which kind of interactive reply the user sent: `button_reply` (tap on an interactive button), `list_reply` (tap on a list row), or `nfm_reply` (a WhatsApp Flow submission). [optional]
interactiveId String WhatsApp only. The `id` of the tapped button or list row, matching the `id` you supplied when the message was sent. Not set for Flow responses. [optional]
buttonPayload String WhatsApp only. Payload attached to a tapped template button. Template buttons emit a plain `button` webhook (not an interactive reply), so `interactiveType` is empty while this field is populated. [optional]
flowResponseJson String WhatsApp only. Raw `nfm_reply.response_json` string returned by a Flow submission. Useful if you need the exact wire payload; for typed access use `flowResponseData` instead. [optional]
flowResponseData Map<String, Object> WhatsApp only. Parsed Flow response JSON. Populated when `flowResponseJson` is valid JSON; otherwise omitted. Keys and value types depend on the specific Flow that was submitted. [optional]

Enum: InteractiveTypeEnum

Name Value
BUTTON_REPLY "button_reply"
LIST_REPLY "list_reply"
NFM_REPLY "nfm_reply"