Agents

Get Agent Session State

Everything needed to render one session from cold.

THREE sources in one answer, and the difference between them matters: messages are the chat bubbles, steps are what the agent actually did (tool calls, reasoning summaries) and work_item_status is whether it is still going. A session driven by a work item has richer steps than messages, and a plain chat has only messages - so a client that renders only one of them will show an empty conversation for half the sessions.

404s on a session the caller cannot see, rather than 403 - existence is not leaked by distinguishing the two.

get/agent/sessions/{session_id}/state

Request

  • Base URL: https://be.graph8.com/api/v1
  • URL: https://be.graph8.com/api/v1/agent/sessions/{session_id}/state
  • Auth: HTTP bearer

Path parameters

session_idstring required

Session id (UUID).

Headers

Authorizationstring nullable
X-Target-Org-Idstring nullable

Response

Successful Response

dataAgentSessionStatePayload required

An open envelope for a hydration or voice answer.

Open because session hydration returns the agent's STEPS as well as its messages, and a step's detail is whatever the tool that produced it reported. That set grows with every tool the platform gains, and a pinned mirror would drop the detail of exactly the newest ones - which on a transcript surface reads as the agent having done less than it did.

Changes

No recorded changes to this operation across all 2 revisions of this API.