Skip to main content

Subject: replyTo accepted (200) but quote not applied on Instagram sends

Feature Request

Hi team,

Following up on this — support confirmed via email that replyTo now works for Instagram sends ("pass the platformMessageId of the message you're quoting, and it will render as a proper inline reply in the customer's Instagram"), and the changelog entry from August 6, 2026 says the same ("Instagram: pass Meta mid"). I implemented it and tested against our real connected account, but the quote does not seem to be applied.

Request sent — POST /v1/inbox/conversations/4618872881457502/messages:

{ "message": "teste diogo", "accountId": "6a7de1bf77555aae0171ed37", "replyTo": "aWdfZAG1faXRlbToxOklHTWVzc2FnZAUlEOjE3ODQxNDAzMzUwNjEwOTE5OjM0MDI4MjM2Njg0MTcxMDMwMTI0NDI1ODYwMTkzODAzNTc4Mjc5NzozMjk1ODExNzEyNDEwNzI5OTc5NTg0Mzc0NzI3OTc5ODI3MgZDZD" }

(the replyTo value is the platformMessageId of an earlier inbound message in the same conversation, "Bom dia teste")

Response received — 200, success:

{ "success": true, "data": { "messageId": "aWdfZAG1faXRlbToxOklHTWVzc2FnZAUlEOjE3ODQxNDAzMzUwNjEwOTE5OjM0MDI4MjM2Njg0MTcxMDMwMTI0NDI1ODYwMTkzODAzNTc4Mjc5NzozMjk1ODkzNzA3NTkwMjMyNTI2MjUyMTk3MDA2MjI2MjI3MgZDZD", "conversationId": "6a7de6e777555aae01737b3f" } }

message.sent webhook received right after — as documented, no metadata field on this event, so no way to confirm the quote from here.

GET /v1/inbox/conversations/4618872881457502/messages?accountId=...&sortOrder=desc&limit=5, called immediately after — the sent message shows up with zero trace of the quote (no metadata, no replyTo, no quotedMessageId field at all on the object):

{ "id": "aWdfZAG1faXRlbToxOklHTWVzc2FnZAUlEOjE3ODQxNDAzMzUwNjEwOTE5OjM0MDI4MjM2Njg0MTcxMDMwMTI0NDI1ODYwMTkzODAzNTc4Mjc5NzozMjk1ODkzNzA3NTkwMjMyNTI2MjUyMTk3MDA2MjI2MjI3MgZDZD", "conversationId": "4618872881457502", "accountId": "6a7de1bf77555aae0171ed37", "platform": "instagram", "message": "teste diogo", "senderId": "17841403350610919", "senderName": "lojabelabruna", "direction": "outgoing", "createdAt": "2026-08-14T11:39:19.318Z", "attachments": [], "isStoryMention": false, "isEdited": false, "editCount": 0, "editHistory": [], "isDeleted": false, "deliveryStatus": "read", "deliveredAt": "2026-08-14T11:39:19.319Z", "readAt": "2026-08-14T11:39:19.319Z", "sentAt": "2026-08-14T11:39:19.318Z" }

(worth noting: this list-messages response shape doesn't match what's documented for this endpoint either — no metadata object present on any message in the array, quoted or not.)

So: request accepted, 200 response, but the reply doesn't appear to be applied anywhere we can check — not in the webhook, not in the messages list. Could you check what's happening server-side with replyTo on Instagram sends for account 6a7de1bf77555aae0171ed37? Happy to send more test payloads if useful.

Thanks!

Posted by Diogo Salvador ·
Status: Completed2 comments

Log in to comment and vote

Comments2

  • Miquel Palet López

    Team•

    Sep 8

    We corrected the misleading Instagram reply guidance and deployed an explicit warning. Meta does not support outbound quoted replies through this Instagram API; inbound quote metadata remains supported.

    If you send replyTo for Instagram or Facebook, the message is sent normally and a successful response now includes a warnings entry with code set to ignored_field and param set to replyTo. The warning explains that the message was sent without a quote. No quote metadata is fabricated. Omit replyTo when sending on these platforms.

    We verified the Instagram flow live, including message readback. The August 6 changelog has also been corrected. Reference: https://docs.zernio.com/messages/send-inbox-message . Changelog: https://docs.zernio.com/changelog

  • Miquel Palet López

    Team•

    Aug 26

    Your test is right and our changelog entry from August 6 was wrong for Instagram. Meta's Instagram Send API has no reply_to parameter: it answers 400 code 100, subcode 2534002 for any mid, including canonical ones taken from Meta's own conversations edge, and we re-verified that on v18.0, v21.0, v23.0 and v25.0. We did ship it once (and reverted it) because reply_to rides in the same POST as the text, so every rejected send lost the message entirely, roughly 50,000 of them in 24 hours. Since then the send path deliberately drops replyTo on Instagram, which is why you get a clean 200 with no quote.

    We are correcting the changelog and the support answer, and we will make the API tell you it was ignored instead of accepting it silently. Instagram quote replies remain inbound-only (you receive them as reply_to.mid on the webhook); on WhatsApp and Telegram replyTo does render a real quote, and on Slack it threads. If Meta ever exposes reply_to for Instagram sends, we will turn it back on.