Skip to main content
GET
List coding sessions
A session groups the nodes that share a root session id, with sub-agent transcripts folded into their parent. Each entry carries live memory and signal counts plus a generated title and summary, which fall back to the opening message until the cached summary is written. Use after and before to bound the activity window.

Authorization

This route requires the read scope. A missing or invalid credential returns 401 authentication_error. A valid credential without the scope returns 403 permission_denied, and the problem body names the exact scope required.

Headers

These are request conventions the contract does not declare as parameters, so they do not appear in the schema tables below.

Success responses

Errors

Every error is an RFC 9457 application/problem+json body carrying a stable code, a requestId, and a suggestedAction where Exo has one. See Errors.

Authorizations

X-Exo-API-Key
string
header
required

An Exo API key (exo_...) sent as the X-Exo-API-Key header.

Query Parameters

limit
integer
default:50
Required range: 1 <= x <= 200
after
string | null

ISO lower bound on last activity

before
string | null

ISO upper bound on last activity

cursor
string | null

Opaque cursor from a previous nextCursor.

pageSize
integer | null

Page size, coerced into [1, 100]. Defaults to the legacy limit parameter when only a cursor is supplied.

Response

The subject's recent sessions, newest activity first.

The response is of type Response Recall Sessions V1 Recall Sessions Get · object.