Skip to content

Support

support_message_list

List messages oldest first — the conversation reads forward.

Tool

support_message_list

List messages oldest first — the conversation reads forward.

List messages oldest first — the conversation reads forward. Name a threadId to read one thread, or omit it to read every thread of this product, which is how a client catches up on what it missed: pass since with the timestamp of the last message it has, then follow nextCursor until it comes back null. Paging is stable across messages that share a timestamp, so a walk neither skips nor repeats one. Filter by direction and by visibility; omit visibility to get public messages and internal notes together. A thread belonging to another product is reported as not found

Behavior

HTTP
GET /support/messages

Arguments

NameTypeRequiredDescription
limitintegerPage size, 1..100 (default 50)
sincestringISO-8601 timestamp. Only messages created strictly after it — pass the createdAt of the last message you already have
cursorstringOpaque position from a previous nextCursor. Resumes exactly where that page ended, with no gap and no repeat even when messages share a timestamp. Never construct one, and do not combine it with offset
offsetintegerNumber of messages to skip. The older pagination, kept for callers that already use it; prefer cursor, which cannot drift as messages arrive
threadIdstringThread whose messages to list. Omit to list the messages of every thread of this product — the catch-up read
directionstringOnly messages in this direction
visibilitystringOnly messages with this visibility. Omit to get both public and internal

Response

FieldTypeAlwaysDescription
limitintegerPage size that was applied
offsetintegerOffset that was applied
messagesarrayThe requested page of messages, oldest first — the conversation reads forward
nextCursorstringPosition to resume from: pass it back as cursor for the next page. Null when this page is the last one

Try it

List messages oldest first — the conversation reads forward.

When to use

List messages oldest first — the conversation reads forward. Name a threadId to read one thread, or omit it to read every thread of this product, which is how a client catches up on what it missed: pass since with the timestamp of the last message it has, then follow nextCursor until it comes back null. Paging is stable across messages that share a timestamp, so a walk neither skips nor repeats one. Filter by direction and by visibility; omit visibility to get public messages and internal notes together. A thread belonging to another product is reported as not found

Example

Ask your agent something like this:

List messages oldest first — the conversation reads forward.

The agent will invoke support_message_list with these arguments:

{}

Esc

Start typing to search the docs.

navigateselect