Skip to main content
Read conversation history after a restart, on a cold start, or when rebuilding a prompt window.
Messages return newest first:
An unsent message keeps its place in sequence order, but projects as a bare tombstone:
Tombstones do not expose parts, fallback text, reactions, or revisions.

Pagination

limit accepts 1 to 100 and defaults to 50. To page backward, pass your lowest sequence as before_sequence.
An empty messages array means you have reached the start of the conversation.

In a group, history is your invocations

A group agent does not read the group transcript. This route returns only the messages inside that agent’s own invocations: each message that invoked it, and each message it committed in reply, including every message of a split reply batch. Messages between other participants never appear, and a group the agent has never been invoked in returns an empty messages array. In a 1:1 conversation the agent reads the whole history its membership covers. Build a group prompt window from what message.received delivers plus this scoped history. Treat an empty page as the start of your scope, not as an empty conversation.

Notes

  • History stays readable while the agent participates in the conversation. Any other case returns 403 forbidden.
  • sequence orders messages within one conversation. It has no relationship to a webhook event_id.
  • History is the recovery path after an event gap or an uncertain delivery.

Next steps