---
title: "Reply Preview Case"
method: GET
path: "/api/app-auto-gtm/projects/{project_id}/reply-preview-case"
tags: ["AppAutoGtm"]
---

# Reply Preview Case

`GET /api/app-auto-gtm/projects/{project_id}/reply-preview-case`

The conversation the reply preview answers — the same case resolution
as POST /reply-preview minus the LLM, so the Replies tab shows the thread
the moment it opens while the draft generates (T-1906, step 2a of the
T-1289 rollout). Real replies only: a project (or pinned ``person_id``)
without a real inbound reply gets ``case: null`` — never a synthetic
inbound (the tab renders its own empty state). Deliberately uncached,
like /reply-preview.

## Path parameters

- `project_id` integer, required

## Query parameters

- `person_id` string, nullable

## Cookies

- `ex_access` string, nullable
- `ex_org` string, nullable

## Response `200`

Successful Response

- ReplyPreviewCaseResponse
  - `case` ReplyPreviewCase — The conversation a reply draft would answer — resolved without any LLM call, so the Replies tab can render it the moment it opens (T-1906); the draft itself still generates separately.
    - `lead_name` string, required
    - `lead_company` string, required
    - `person_id` string
    - `thread` object[]

## Other responses

- `422` — Validation Error

---

[API](https://skmtc.dev/explee/apis/explee-api.md) · [All operations](https://skmtc.dev/explee/apis/explee-api/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/explee/explee-api/revisions/f169bc6e9447/schema)