# List Team Run Checkpoints (/reference-api/schema/teams/list-team-run-checkpoints)

## Team storage and identity [#team-storage-and-identity]

Use the database-backed [example Team server](/reference-api/schema/teams/create-team-run#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 [#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](/reference-api/schema/teams/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.

## `GET /teams/{team_id}/runs/{run_id}/checkpoints`

**Summary:** List Team Run Checkpoints

**Description:** List FE-friendly continuation boundaries derived from the current stored team run. No separate checkpoint table is used; entries are inferred from message-level checkpoint markers and the terminal end of the transcript.

### Authentication

- Option 1: `HTTPBearer` — HTTP bearer

### Parameters
- `run_id` (path; string; required)
- `team_id` (path; string; required)
- `session_id` (query; string; required) — Session ID for the run

### Request body

None.

### Responses

#### `200`

Run checkpoints retrieved successfully

**`application/json`**

Type `unspecified`.

#### Other responses

- `400` — Bad Request `application/json`: Schema `BadRequestResponse` (object).
- `401` — Unauthorized `application/json`: Schema `UnauthenticatedResponse` (object).
- `404` — Team or run not found `application/json`: Schema `NotFoundResponse` (object).
- `422` — Validation Error `application/json`: Schema `ValidationErrorResponse` (object).
- `500` — Internal Server Error `application/json`: Schema `InternalServerErrorResponse` (object).