Skip to main content

This change contains a deprecation of the external_conversation_id property in the metadata object.

You can now reply to specific messages through application channels.

{
"type": "message",
"payload": {
[MESSAGE BODY]
},
"metadata": {
"external_conversation_ids": string[], // External identifier of the conversations related to this message.
"referenced_message_external_id": string // (Optional) ID of the message being referenced as a direct reply
}
}

As part of this change, we are introducing two new properties in the metadata object used when creating or replying to messages in a channel:

  • external_conversation_ids—a string array containing the external conversation identifiers, which you use when creating or receiving messages. This property replaces external_conversation_id, which is now deprecated in the metadata object. This change allows you to send multiple external conversation IDs instead of just one.
  • reference_message_external_id—the external identifier of the message you want to reply to.


Please refer to our Developer Portal for more details, or let us know if you have questions in the comments!

 

Happy coding!

When are you making this switch? ​@dedarritchon 


Hi @roofquotes,

The reply feature is already live. Regarding the external_conversation_id field deprecation, the exact date has not been set yet. We will provide at least 3 months’ notice before it’s removed so developers have time to update their implementations.

Best,


Reply