spec 1 linked patterns checked
Slack Developer Docs: conversations.replies
Documents retrieving a cursor-paginated thread of messages posted to a conversation, required channel and thread timestamp arguments, parent thread timestamp, parent user id, reply count, subscribed state, last read, unread count, has_more, next cursor, and access errors.
Read with a purpose
What this source can teach
Use this source to check a technical or accessibility requirement against its exact wording and scope.
- Start with the original. Open the source and find the guidance or example relevant to your task.
- Trace the connection. Use the claim notes below to see how this site applies the source to specific patterns.
- Check the setting. Compare the source's platform, people, and constraints with your own decision.
Pattern Decisions This Source Supports
| Pattern | Supported decision | Required contract | Claim note |
|---|---|---|---|
| Threaded discussion | Choose threaded discussion when the core unit is a topic or parent message with replies that need branch context and participation state. | Starting a reply records the exact parent topic or parent reply being answered and shows that target while composing. | Slack API supports thread message retrieval with parent timestamp, parent user id, reply count, subscribed state, last-read and unread counts, cursor pagination, has_more, and access errors. |
Evidence Role
This source is treated as spec evidence. Its value comes from the specific claims and setting described above.
Publisher: Slack Developer Docs. Last checked: .