Get Team Run Checkpoint Snapshot

Team storage and identity

Use the database-backed example Team server. Keep the Team run's returned run_id and session_id; a nested member run is not interchangeable with the Team run. Stored run, checkpoint and session operations require the configured database.

JWT user isolation is opt-in; non-admin service-account PAT callers always self-scope. Scoped callers need their own matching Team session and run, while configured resource authorization also applies. Run and checkpoint lookups return 404 for inaccessible or mismatched records. For factories, retain any factory_input needed by endpoints that reconstruct the Team.

Select the message boundary

First call List Team Run Checkpoints. Use an entry's message_index in this path, not its checkpoint_id display label. The same boundary is named continue_from when continuing a run.

The snapshot is derived from a copy and does not rewrite the stored run. Safe truncation around tool-call/result pairs can return fewer messages than the requested boundary, while the checkpoint metadata still names that requested boundary. Inspect the returned messages before using the snapshot as a transcript.

GET/teams/{team_id}/runs/{run_id}/checkpoints/{message_index}

Return a derived team run snapshot truncated at a message boundary. Use the returned message_index as continue_from when continuing this run.

Authorization

HTTPBearer
AuthorizationBearer <token>

In: header

Path Parameters

team_id*Team Id
run_id*Run Id
message_index*Message Index

Query Parameters

session_id*Session Id

Session ID for the run

Response Body

application/json

application/json

application/json

application/json

application/json

application/json

curl --request GET 'https://example.com/teams/string/runs/string/checkpoints/0?session_id=string'
null