Skip to main content
Quick Reference - Send a threaded message and fetch thread replies:
Available via: SDK | REST API | UI Kits
Messages that are started from a particular message are called Threaded Messages or simply threads. Each thread is attached to a message which is the parent message for that thread.

Send Message in a Thread

As mentioned in the Send a Message section, you can either send a message to a user or a group based on the receiverType and the UID/GUID specified for the message. A message can belong to any of the following types:
  1. Text Message
  2. Media Message
  3. Custom Message
Any of the above messages can be sent in a thread. A thread is identified based on the parent message, so while sending a message the parentMessageId must be set to indicate that the message belongs to the thread with the specified parentMessageId. This can be achieved using the setParentMessageId() method provided by the object of the TextMessage, MediaMessage, and CustomMessage class. The id specified in the setParentMessageId() method maps the message sent to the particular thread.
The parentMessageId is dynamic and corresponds to the actual id of the parent message you want to reply to. In the code examples below, we use placeholder values like 100 or 1, but in practice, you’ll use the actual message ID obtained from your message list or real-time listener.
Example to send a text message in a thread in a user conversation:
The above snippet shows how a message with the text “Hello” can be sent in the thread with parentMessageId 100. Similarly, using the setParentMessageId() method, Media and Custom Messages can be sent in threads too.
On SuccesssendMessage() returns the sent threaded message with parentMessageId:Message Object:
sender Object:
receiver Object:
data Object:
data.entities Object:
data.entities.sender Object:
data.entities.sender.entity Object:
data.entities.receiver Object:
data.entities.receiver.entity Object:
data.metadata Object:
data.metadata.@injected Object:
data.metadata.@injected.extensions Object:
data.metadata.@injected.extensions.link-preview Object:
metadata Object:
metadata.@injected Object:
metadata.@injected.extensions Object:
metadata.@injected.extensions.link-preview Object:

Receiving Real-Time Messages

The procedure to receive real-time messages is exactly the same as mentioned in the Receive Messages section. This can be achieved using the MessageListener class provided by the SDK. To add a MessageListener, you can use the addMessageListener() method of the SDK. The only thing that needs to be checked is if the received message belongs to the active thread. This can be done using the parentMessageId field of the message object.
Remember to remove your listener on unmount. Always call CometChat.removeMessageListener("UNIQUE_LISTENER_ID") when the component unmounts (e.g., in a useEffect cleanup or componentWillUnmount) to avoid memory leaks and duplicate event handling.

Fetch All Messages for a Thread

You can fetch all the messages belonging to a particular thread by using the MessagesRequest class. To get an object of the MessagesRequest class, use the MessagesRequestBuilder class and call the setParentMessageId() method to inform the SDK that you only need the messages belonging to the thread with the specified parentMessageId. Once you have the object of the MessagesRequest class, call the fetchPrevious() method to get the latest messages in the thread. In one call, a maximum of 100 messages can be fetched. To fetch the next set of messages, call the fetchPrevious() method again on the same object.
On SuccessfetchPrevious() returns an array of messages belonging to the thread:Message Object (per item in array):
sender Object:
receiver Object:
data Object:
data.entities Object:
data.entities.sender Object:
data.entities.sender.entity Object:
data.entities.receiver Object:
data.entities.receiver.entity Object:
data.metadata Object:
data.metadata.@injected Object:
data.metadata.@injected.extensions Object:
data.metadata.@injected.extensions.link-preview Object:
metadata Object:
metadata.@injected Object:
metadata.@injected.extensions Object:
metadata.@injected.extensions.link-preview Object:

Avoid Threaded Messages in User/Group Conversations

While fetching messages for normal user/group conversations using the MessagesRequest, threaded messages will be included in the list by default. To exclude threaded messages from the list of user/group messages, use the hideReplies() method of the MessagesRequestBuilder class. This method takes a boolean argument which, when set to true, excludes messages belonging to threads from the list of messages.
Without hideReplies(true)fetchPrevious() returns all messages including thread replies (note the second message has parentMessageId):Message Object (per item in array):Thread replies in the same response will have a parentMessageId field linking them to their parent message.
sender Object:
receiver Object:
data Object:
data.entities Object:
data.entities.sender Object:
data.entities.sender.entity Object:
data.entities.receiver Object:
data.entities.receiver.entity Object:
data.metadata Object:
data.metadata.@injected Object:
data.metadata.@injected.extensions Object:
data.metadata.@injected.extensions.link-preview Object:
metadata Object:
metadata.@injected Object:
metadata.@injected.extensions Object:
metadata.@injected.extensions.link-preview Object:
On SuccessfetchPrevious() returns messages excluding thread replies (note: parent messages with replyCount are included, but their replies are not):Message Object (per item in array):
sender Object:
receiver Object:
data Object:
data.entities Object:
data.entities.sender Object:
data.entities.sender.entity Object:
data.entities.receiver Object:
data.entities.receiver.entity Object:
data.metadata Object:
data.metadata.@injected Object:
data.metadata.@injected.extensions Object:
data.metadata.@injected.extensions.link-preview Object:
metadata Object:
metadata.@injected Object:
metadata.@injected.extensions Object:
metadata.@injected.extensions.link-preview Object:
The above snippet will return messages between the logged-in user and cometchat-uid-1 excluding all the threaded messages belonging to the same conversation.

Best Practices and Troubleshooting

Every message object has a parentMessageId field. If this field is set (non-zero), the message is part of a thread. Use message.getParentMessageId() to retrieve the parent message ID and match it against the active thread.
By default, MessagesRequest includes threaded messages. Use the hideReplies(true) method on MessagesRequestBuilder when fetching messages for the main conversation to exclude thread replies.
You can fetch a maximum of 100 messages per fetchPrevious() call. Use the setLimit() method on MessagesRequestBuilder to control the number of messages returned. To load more messages, call fetchPrevious() again on the same MessagesRequest object.
Yes. The setParentMessageId() method is available on TextMessage, MediaMessage, and CustomMessage objects. Set the parent message ID before calling CometChat.sendMessage() to send any message type within a thread.

Next Steps

Send a Message

Learn how to send text, media, and custom messages to users and groups.

Receive Messages

Set up real-time message listeners and fetch message history.

Message Filtering

Filter messages by type, category, tags, timestamps, and more.

Message Structure

Understand message categories, types, and the message hierarchy.