Agents

Mark Agent Session Read

Mark messages read up to a COUNT, not a flag.

A count higher than the session actually holds is refused with 409 rather than accepted. That looks strict until you consider what accepting it does: a stale client claiming to have read eleven messages when there are nine would mark the next two read before anyone saw them, and the customer would never be told the agent had replied.

The app answers 204 with no body; this returns the usual envelope so a generated SDK has one response shape across the surface.

put/agent/sessions/{session_id}/read

Request

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

Path parameters

session_idstring required

Session id (UUID).

Headers

Authorizationstring nullable
X-Target-Org-Idstring nullable

Request body

message_countinteger required

How many messages the caller has actually seen. NOT a flag: the server refuses a count higher than the session holds with a 409, because a client claiming to have read messages that do not exist yet is a stale client, and silently accepting it would mark a later real message read before anyone saw it.

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.