ReferenceHTTP APISessions

Download one file the session left under out/

GET
/v1/sessions/{id}/outputs/{path}

Streams one file that GET /v1/sessions/{id}/outputs lists, as application/octet-stream with Content-Disposition: attachment and X-Content-Type-Options: nosniff. {path} is the listed path exactly, percent-encoded as one path segment (out/report.md is out%2Freport.md). The bytes are the ones the checkpoint verified; if the store no longer holds them the transfer ends early with an error rather than completing with other bytes, so check the length (or sha256) of what arrived. A path the list does not name, a file listed with omitted, or a session with no committed checkpoint answers 404.

Scope: sessions:read (API key or cookie session).

Authorization

headerAuthorizationBearer <token>

For servers and scripts: an API key sent as an HTTP bearer token, Bearer <key>. It holds exactly the scopes it was issued with; a key issued before scopes existed holds none. It never needs the CSRF header, and it cannot manage agents, members, teams or API keys. Issue one in the web console under Settings → API keys; each operation names the scope it needs.

Scope: sessions:read

Path Parameters

id*string

The session's id.

Match^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$
Formatuuid
path*string

The path the outputs list gives, percent-encoded as one segment (out/report.md is out%2Freport.md).

Length1 <= length <= 4096

Response Body

The file's bytes.

response?stringapplication/octet-stream
Example Request
curl -X GET 'https://example.com/v1/sessions/497f6eca-6276-4993-bfeb-53cbbbba6f08/outputs/string'
Example Response
"string"