Struct SendInboxMessageRequestInteractive 

pub struct SendInboxMessageRequestInteractive {
    pub type: Type,
    pub header: Option<Box<SendInboxMessageRequestInteractiveHeader>>,
    pub body: Box<SendInboxMessageRequestInteractiveBody>,
    pub footer: Option<Box<SendInboxMessageRequestInteractiveFooter>>,
    pub action: Box<SendInboxMessageRequestInteractiveAction>,
}

SendInboxMessageRequestInteractive : WhatsApp-only. Rich interactive payload for list messages, CTA URL buttons, and Flow prompts. When set, takes priority over buttons and quickReplies. The shape mirrors Meta’s Cloud API interactive object verbatim, so any payload that works against Meta directly will also work here. Use buttons / quickReplies for simple button replies (WhatsApp’s interactive.type: \"button\") — the abstraction caps at 3 buttons and handles the auto-conversion for you. Use this field only for list, cta_url, or flow messages. Tap events come back via the message.received webhook with metadata.interactiveType set to list_reply or nfm_reply.

Fields

type: Type

Which interactive layout to render.

header: Option<Box<SendInboxMessageRequestInteractiveHeader>>

body: Box<SendInboxMessageRequestInteractiveBody>

footer: Option<Box<SendInboxMessageRequestInteractiveFooter>>

action: Box<SendInboxMessageRequestInteractiveAction>

Implementations

impl SendInboxMessageRequestInteractive

pub fn new( type: Type, body: SendInboxMessageRequestInteractiveBody, action: SendInboxMessageRequestInteractiveAction, ) -> SendInboxMessageRequestInteractive

WhatsApp-only. Rich interactive payload for list messages, CTA URL buttons, and Flow prompts. When set, takes priority over buttons and quickReplies. The shape mirrors Meta’s Cloud API interactive object verbatim, so any payload that works against Meta directly will also work here. Use buttons / quickReplies for simple button replies (WhatsApp’s interactive.type: \"button\") — the abstraction caps at 3 buttons and handles the auto-conversion for you. Use this field only for list, cta_url, or flow messages. Tap events come back via the message.received webhook with metadata.interactiveType set to list_reply or nfm_reply.

Trait Implementations

impl Clone for SendInboxMessageRequestInteractive

fn clone(&self) -> SendInboxMessageRequestInteractive

Returns a duplicate of the value.

fn clone_from(&mut self, source: &Self)

Performs copy-assignment from source.

impl Debug for SendInboxMessageRequestInteractive

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.

impl Default for SendInboxMessageRequestInteractive

fn default() -> SendInboxMessageRequestInteractive

Returns the “default value” for a type.

impl<'de> Deserialize<'de> for SendInboxMessageRequestInteractive

fn deserialize<__D>(__deserializer: __D) -> Result<Self, __D::Error>

where __D: Deserializer<'de>,

Deserialize this value from the given Serde deserializer.

impl PartialEq for SendInboxMessageRequestInteractive

fn eq(&self, other: &SendInboxMessageRequestInteractive) -> bool

Tests for self and other values to be equal, and is used by ==.

fn ne(&self, other: &Rhs) -> bool

Tests for !=. The default implementation is almost always sufficient, and should not be overridden without very good reason.

impl Serialize for SendInboxMessageRequestInteractive

fn serialize<__S>(&self, __serializer: __S) -> Result<__S::Ok, __S::Error>

where __S: Serializer,

Serialize this value into the given Serde serializer.

impl StructuralPartialEq for SendInboxMessageRequestInteractive