List Team Run Checkpoints

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.

Checkpoint identifiers

The response contains run_id, session_id and a checkpoints array. Each entry has a one-based string checkpoint_id for display and a message_index/continue_from message boundary for API calls. They are different values.

Use message_index for Get Team Run Checkpoint Snapshot, and continue_from when selecting a continuation boundary. Checkpoints are derived from the saved Team run's messages; they do not establish an independent backup of that run.

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

null

{  "detail": "string",  "error_id": "string",  "error_type": "string"}

{  "detail": "string",  "error_id": "string",  "error_type": "string"}

{  "detail": "string",  "error_id": "string",  "error_type": "string"}

{  "detail": "string"}

{  "detail": "string",  "error_id": "string",  "error_type": "string"}