Skip to main content
POST

Card structure

Card with quick reply buttons

Do not include the type field at the card level when using quick_reply buttons. It must only be set when the action is cta_url. Including it on cards with quick_reply causes Meta to reject the message with a 400/500 error.

quick_reply button fields

Restrictions

  • Cards: minimum 1, maximum 10 per carousel.
  • Header: only image or video are supported.
  • Compatible providers: WhatsApp Cloud API and Gupshup CAPI.
This is an interactive carousel sent inside an active WhatsApp session. It does not require an HSM template approved by Meta.

Use Cases

  • Product catalogs with CTA to the store
  • Plan or service comparisons
  • Multiple promotions with purchase buttons
  • Quick selection between options with associated image

Authorizations

Authorization
string
header
required

Basic authentication using Base64 encoded clientId:clientSecret

Path Parameters

botId
string
required

The unique identifier of the bot

Body

application/json

Message payload. The structure varies based on the message type.

type
enum<string>
required

Type of message to send

Available options:
text
Example:

"text"

userId
string
required

Unique identifier of the user receiving the message. Accepts either a phone number in E.164 format without the leading '+' (e.g. '593999999999') or a BSUID (Business-Scoped User ID, e.g. 'US.13491208655302741918') for users who have enabled phone number privacy in WhatsApp.

Example:

"593999999999"

text
string
required

Text content of the message

Example:

"Hello, this is a text message"

botId
string

Unique identifier of the bot sending the message

Example:

"BOT_ID"

Response

Message sent successfully

success
boolean
Example:

true

messageId
string
Example:

"msg_123456789"