List Team Runs

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.

The response is a bare array of Team run projections, without pagination metadata. These projections use run_input and ISO 8601 created_at; the raw single-run polling response uses a different representation.

Pass session_id and optionally an exact uppercase status: PENDING, RUNNING, COMPLETED, ERROR, PAUSED, CANCELLED or REGENERATED. Lowercase or unknown strings currently match nothing and return an empty array. Remote Team run listing is unsupported (400).

curl --request GET 'https://example.com/teams/string/runs?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"}