---
title: "Get Agent Session State"
method: GET
path: "/agent/sessions/{session_id}/state"
tags: ["Agents"]
---

# Get Agent Session State

`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

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.

## Path parameters

- `session_id` string, required: Session id (UUID).

## Headers

- `Authorization` string, nullable
- `X-Target-Org-Id` string, nullable

## Response `200`

Successful Response

- ApiResponseAgentSessionStatePayload
  - `data` AgentSessionStatePayload, 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.
  - `pagination` PaginationMeta
    - `page` integer, required: Current page number (1-indexed)
    - `limit` integer, required: Items per page
    - `total` integer, required: Total number of items
    - `has_next` boolean, required: Whether there are more pages
    - `next_cursor` string, nullable: Opaque cursor for the next page; null when there are no more items. Pass it back as the `cursor` query param to fetch the following page without computing page numbers.
    - `total_available` integer, nullable: Search endpoints only: how many records really match, when known. Can be larger than `total`, which is capped at the 10,000 results that can be paged. For company search this is a distinct-company estimate. Null when unknown; absent outside search.
    - `total_is_lower_bound` boolean, nullable: Search endpoints only: true when more records match than `total` shows (the result set is larger than the 10,000 results that can be paged). Absent outside search.
    - `notes` string[], nullable: Search endpoints only: plain-language notes about the result, e.g. that more records match than can be paged, or that a reversed `between` range was put in order.

## Other responses

- `422`: Validation Error

---

[API](https://skmtc.dev/graph8/apis/graph8-developer-api.md) · [All operations](https://skmtc.dev/graph8/apis/graph8-developer-api/llms.txt) · [OpenAPI document](https://skmtc.dev/graph8/apis/graph8-developer-api/revisions/2e7cfa0ca921?raw)