Skip to main content
GET
List sessions
Returns a paginated list of sessions visible to the authenticated user. Results are sorted by creation date (newest first) by default. Returns a paginated list of Session summary objects.

Query parameters

page
integer
default:"1"
Page number (1-based).
size
integer
default:"10"
Items per page. Maximum: 100.
sort
string
default:"-created_at"
Sort order. Options: created_at, -created_at.
status
string[]
Filter by session status. Multi-value. Values: queued, pending, running, paused, idle, awaiting_tool_results, completed, failed, timed_out, interrupted.
agent
string[]
Filter by agent identifier. Multi-value. Example: web-price-finder.
group_id
string
Filter by group ID. Returns all sessions tagged with this group.
parent_session_id
string
Filter by parent session ID. Returns only child sessions of the given parent.
schedule_id
string
Filter by schedule ID. Returns only sessions created by that schedule’s fires.
Case-insensitive match on the session’s first message or answer.
created_before
string
Only sessions created before this timestamp (ISO 8601).
created_after
string
Only sessions created after this timestamp (ISO 8601).
finished_before
string
Only sessions that finished before this timestamp (ISO 8601).
finished_after
string
Only sessions that finished after this timestamp (ISO 8601).
owner
string
default:"me-in-organization"
Access scope: me (your sessions anywhere), me-in-organization (your sessions in the current org), organization (everyone’s sessions in the org), or me-or-organization.

Examples

List your recent sessions

Response

Filter by status and agent

List all sessions in a group

Find the subagents a session spawned

Multi-agent runs delegate work to child sessions. The parent’s status lists their IDs in subagent_session_ids; pass the parent’s ID to parent_session_id to pull the whole roster in one call, each child labeled with the agent that ran it. Walk deeper trees by recursing on a child’s own ID.
Response
Each child is a session like any other: open it by id to poll its status, read its answer from /changes, or replay its events.