---
title: "Api Get Edit Chat"
method: GET
path: "/api/apps/{app_id}/edit-chat"
tags: ["apps"]
---

# Api Get Edit Chat

`GET /api/apps/{app_id}/edit-chat`

## Request

- Base URL: `https://app.getdot.ai` (the document declares no server; this is the origin it was published from)
- URL: `https://app.getdot.ai/api/apps/{app_id}/edit-chat`
- Auth: one of:
  - API key in header `X-API-KEY`
  - API key in cookie `Authorization`
  - OAuth 2 (password, token URL `/api/auth/token`)

Find the conversation that built this app, for the current user.

Returns the user's OLDEST chat bound to this app — the conversation
that initially created it (`set_chat_dashboard_id` stamps the creating
chat at first publish) — so Edit always returns to the build thread
rather than whichever tweak session happened to be most recent.
Ask-mode chats live under `additional_metadata.app_context` and never
match this lookup.

Returns { chat_id } — null when no edit chat exists. "No chat yet" is
the normal state for most apps, not an error: as a 404 it printed a
browser console error on every such Edit-resume lookup, which tripped
zero-console-error E2E gates and looked like a bug to users' devtools.

## Path parameters

- `app_id` string, required

## Response `200`

Successful Response

- object

## Other responses

- `422`: Validation Error

---

[API](https://skmtc.dev/getdot/apis/dot-api-2.md) · [All operations](https://skmtc.dev/getdot/apis/dot-api-2/llms.txt) · [OpenAPI document](https://skmtc.dev/getdot/apis/dot-api-2/revisions/d26fe7163a7f?raw)