The Open Messaging API endpoint POST /api/v2/conversations/{conversationId}/messages accepts the payload but the agent sees the quick replies as static text instead of clickable buttons. I’m sending the standard structured message format documented for cards and quick replies.
{
"from": {
"id": "guest-123",
"name": "Guest"
},
"text": "Select an option",
"quickReplies": [
{
"text": "Billing",
"payload": "billing_inquiry"
},
{
"text": "Support",
"payload": "tech_support"
}
]
}
The response is a 200 OK with the message ID. The guest client also shows it as text. We’re using the latest version of the Web Messaging SDK on the embed side. I’ve checked the message direction and it’s inbound. Is there a specific content-type header I’m missing or a version constraint on the Open Messaging API that breaks quick replies? The docs don’t mention any limitations on button rendering for inbound structured messages.