---
title: "List Reviews"
method: GET
path: "/internal/evals/rollout-consistency/sweeps/{sweep_id}/reviews"
tags: ["internal"]
---

# List Reviews

`GET /internal/evals/rollout-consistency/sweeps/{sweep_id}/reviews`

## Request

- Base URL: `https://api.kobaltlabs.com` (the document declares no server; this is the origin it was published from)
- URL: `https://api.kobaltlabs.com/internal/evals/rollout-consistency/sweeps/{sweep_id}/reviews`
- Auth: none declared

Staff marks on this sweep, for polling while operators go through the worklist together.

Separate from the detail response: a finished sweep's figures never change, but the marks do,
and re-fetching the worklist every few seconds to learn who ticked a row would be the wrong
payload for that question.

## Path parameters

- `sweep_id` string, uuid, required

## Response `200`

Successful Response

- ReviewMark[]
  - `review_id` string, uuid, required
  - `sweep_id` string, uuid, required
  - `subject_kind` 'rule_drift' | 'low_signal' | 'regression' | 'item', required: What a collaborative review mark is attached to on one sweep. Four kinds, kept apart because a requirement can show up on both the drift worklist and the low-signal list, and a mark on one is not a mark on the other. The id is the row the dashboard already uses as the key: `requirement_id` for the two rule lists, `regression_id` for a baseline risk, `item_id` for a piece of collateral.
  - `subject_id` string, uuid, required
  - `reviewed_by_user_id` string, uuid, nullable, required
  - `reviewed_by_email` string, required
  - `reviewed_by_name` string, required
  - `reviewed_at` string, date-time, required

## Other responses

- `422`: Validation Error

---

[API](https://skmtc.dev/kobaltlabs/apis/fastapi.md) - [All operations](https://skmtc.dev/kobaltlabs/apis/fastapi/llms.txt) - [OpenAPI document](https://skmtc.dev/kobaltlabs/apis/fastapi/revisions/8587332d5e43?raw)