---
title: "Get Email Thread Review"
method: GET
path: "/api/v1/email-threads/{email_thread_id}/review"
tags: ["email-thread-reviews"]
---

# Get Email Thread Review

`GET /api/v1/email-threads/{email_thread_id}/review`

Return the current user's review of this thread, or 404 when absent.

## Path parameters

- `email_thread_id` string, uuid, required

## Response `200`

Successful Response

- EmailThreadReviewRead
  - `id` string, uuid, required
  - `email_thread_id` string, uuid, required
  - `reviewer_user_id` string, uuid, required
  - `verdict` 'good' | 'par' | 'bad', required — Reviewer's coarse verdict on the whole call (V0.5). The three values cover the spectrum without overclassifying: the agent nailed it, met the bar, or fell short. Annotations carry the signal — the verdict is a coarse summary only. See ``sync_review_to_findings.py`` for the uniform "verdict + 0 annotations → 0 findings" rule (intentional extension beyond the briefing's §9, which only guaranteed it for good/par; V0.5 extends it to bad so the sync function has one consistent rule).
  - `outcome` string, required

## Other responses

- `404` — Email thread or review not found
- `422` — Validation Error

## Changes

> 26 revisions in range; 1 not diffed.

- **2026-09-03** `d65b8fefae34` — 2 info
  - added the optional property `detail/items/ctx` to the response with the `422` status
  - added the optional property `detail/items/input` to the response with the `422` status

[Change history](https://skmtc.dev/getanana/apis/cleon-api/changes/api/v1/email-threads/:email_thread_id/review/get.md)

---

[API](https://skmtc.dev/getanana/apis/cleon-api.md) · [All operations](https://skmtc.dev/getanana/apis/cleon-api/llms.txt) · [OpenAPI document](https://skmtc.dev/getanana/apis/cleon-api/revisions/4df7b22a7dae?raw)