Meeting SDK Feature Request: Add thread id to onReceivedChatMsg payload

Feature Requests
1

Cross-posting from the Meeting SDK forum in case that’s not the correct place for feature requests:

Thanks for adding the onReceiveChatMsg callback in Meeting SDK v3.12.0 , that was a missing piece for us and is super helpful for our app! One piece that is missing and I’m hoping you can add in a follow-up release is a way to differentiate a reply in a thread from a normal chat message. The format of the payload isn’t documented yet, but looks like this from my testing:

{
  "sender": "Zach Waugh",
  "senderId": 16778240,
  "senderGuid": "5D902C75-51A2-76E1-2689-18941E49F752",
  "timestamp": "05:00 PM",
  "receiver": "Everyone",
  "receiverId": "",
  "type": "text",
  "content": {
    "text": "reply to new thread",
    "messageId": "1-{076e06d6-0eb0-4fb2-a797-b46efc6ccd46}",
    "chatType": "groupchat",
    "messageType": "0",
    "t": "1742590810290"
  }
}

That was for a reply, but there’s no way to know it was a reply. Would it be possible to add a threadId or parentId parameter that would correspond to the messageId of the parent message of the thread? Thanks!

2 Likes
2

Thanks for sharing this! The onReceiveChatMsg callback in Meeting SDK v3.12.0 has been a great addition, and I completely agree that distinguishing between normal chat messages and threaded replies would be really helpful.

It looks like the current payload doesn’t include any clear identifier for replies, which makes it tricky to handle threaded messages properly. Adding a threadId or parentId field linking replies to their original messages would be a solid improvement. That way, apps could easily organize chats and display threads correctly.

It’d be great if the Zoom team could consider this for an upcoming release. Hopefully, they can confirm if this is on the roadmap or if there’s already an undocumented way to differentiate replies. Looking forward to any updates on this.

Thanks again for bringing this up!