List or stream ordered thread events

GET/v1/threads/{threadId}/events

For JSON, no cursor returns the newest page in chronological order, after pages forward, and before (or legacy alias cursor) pages backward. For SSE, an explicit after or Last-Event-ID resumes after that sequence; without either the stream starts at the current head and emits only future events. SSE event IDs equal the committed thread sequence.

How to call this endpoint

Every ACP API request uses bearer authentication. The examples here show the actual request path, auth header, and body shape that the platform expects.

Path, query, and header parameters

These parameters control which ACP object the endpoint acts on and how the request is processed.

Path parameters
NameLocationTypeRequiredDescription
threadIdpathstringYesThread ID
Query parameters
NameLocationTypeRequiredDescription
afterqueryintegerNoReturn events with a sequence strictly greater than this cursor.
beforequeryintegerNoReturn the newest events with a sequence strictly less than this cursor.
cursorqueryintegerNoBackward-compatible alias for `before`.
limitqueryintegerNo
streamquerybooleanNo

Body schema

This endpoint does not require a request body.

None.

What the API returns

Each response code below includes the documented payload shape for the ACP API.

200Ordered event page or replayable event streamapplication/json
FieldTypeRequiredDescription
objectstringNo
threadIdstringNoThread ID.
dataobject[]No
nextCursorintegerNo
streamCursorintegerNoHighest sequence returned; use as `after` or SSE resume cursor.
olderCursorintegerNoLowest sequence returned; use as `before` to load an older page.
latestSequenceintegerNo
hasOlderbooleanNo
hasNewerbooleanNo
hasMorebooleanNoAlias for hasOlder on latest/older pages and hasNewer on forward pages.
directionlatest | forward | olderNo
List or stream ordered thread events
Loading...
Response 200
Loading...
See the ACP quickstart and SDK flow