Agent Sessions
Get Session Transcript
Get a renderable transcript for a session
GET
Returns a snapshot of a session as a renderable timeline. Use this endpoint when you want to show the full conversation without reconstructing user messages, assistant messages, and tool calls from the raw event ledger.
Compared with List/Send Session Events:
For live updates, stream
- Event endpoints are ledger-first (append and inspect canonical events).
- Transcript is UI-first (pre-shaped timeline items for rendering).
- Event endpoints are best for ingestion, auditing, and idempotent writes.
- Transcript is best for chat/history views and quick replay of a session state.
GET /v1/sessions/{session_id}/stream and refetch the transcript after new events arrive.
Path Parameters
Session ID.
Headers
Bearer token using your Dari API key.
Response Fields
The agent that owns the session.
The current session record, including lifecycle status and most recent message references.
Renderable transcript items in display order. Each item has a
type field that determines its shape.One of
user_message, assistant_message, or tool_call.Message ID for the user turn this timeline item belongs to.
ISO 8601 timestamp for when this timeline item was created.
User Message Items
For
user_message items, this is the ordered user-supplied content, such as text, file, or image blocks.Assistant Message Items
For
assistant_message items, the current message status: queued, running, waiting_for_tool, completed, or failed.For
assistant_message items, this is the assistant response content available so far. It is empty while the message is still queued or running.For failed assistant messages, the error message if one is available.
Tool Call Items
For
tool_call items, the tool call ID.For
tool_call items, the tool name.For
tool_call items, the arguments sent to the tool.For
tool_call items, the current tool status: requested, running, completed, or failed.For completed or failed
tool_call items, the tool result or error payload when available.For
tool_call items, whether the result represents an error.For completed or failed
tool_call items, the ISO 8601 completion timestamp when available.Errors
A missing or invalid API key returns401. If the session does not exist, the API returns 404. If the API key belongs to a different organization than the session, the API returns 403.