Threads and replies provide your users with a way to go into more detail about a specific topic.

This can be very helpful to keep the conversation organized and reduce noise. To create a thread you simply send a message with a parent_id. Have a look at the example below:

Messages inside a thread can also have reactions, attachments and mention as any other message.

When you read a channel you do not receive messages inside threads. The parent message includes the count of replies which it is usually what apps show as the link to the thread screen. Reading a thread and paginating its messages works in a very similar way as paginating a channel.

Instead of replying in a thread, it's also possible to quote a message. Quoting a message doesn't result in the creation of a thread; the message is quoted inline.

To quote a message, simply provide the quoted_message_id field when sending a message:

Based on the provided quoted_message_id, the quoted_message field is automatically enriched when querying channels with messages. Example response:

It is possible to query the list of threads that current user is participant of. This is useful to create thread list similar to what Slack or Discord has. Response will include threads with unread replies first, sorted by the latest reply timestamp in descending order. Threads with no unread replies will follow, also sorted by the latest reply timestamp in descending order.

You can also paginate over the thread list or request specific number of latest replies per thread.

Following is the list of supported options for querying threads:

ThreadManager class offers built-in pagination handling for threads with own state store to access loaded threads. To access threads you can either subscribe to the ThreadManager state or access the latest value by calling getLatestValue on state property of the ThreadManager.

Each thread instance comes with registerSubscriptions method which registers handlers to appropriate thread-related events. With subscriptions registered, the updates to the state are done automatically and can be accessed by subscribing to the state updates.

If you're using ThreadManger to manage your list of threads, you can call registerSubscriptions method on the manager instance and the manager will automatically handle subscriptions (registration and cleanup) of the added and removed threads.

This endpoint returns a thread by the given threadId.

You can assign a title and any additional custom data to each thread.

Similarly to remove any custom property from thread:

Total number of unread threads is available in response of connectUser endpoint

If you would like to mark specific thread as read or unread, you can do that as following

To get unread count per thread for a current user, you can use the getUnreadCount endpoint as following