---
title: "Reset Capture Disposition"
method: POST
path: "/api/chats/{chat_id}/capture-disposition/reset"
tags: ["chats"]
---

# Reset Capture Disposition

`POST /api/chats/{chat_id}/capture-disposition/reset`

## Request

- Base URL: `https://app.thinqos.com` (the document declares no server; this is the origin it was published from)
- URL: `https://app.thinqos.com/api/chats/{chat_id}/capture-disposition/reset`
- Auth: none declared

TOS-3758: hand this capture back to its connection's archive/read policy.

The undo half of "Using connection default". Manually archiving or
restoring ONE capture stamps
``chat_participants.capture_archive_manually_changed_at``, after which every
CAS-guarded automated pass in ``services/capture_disposition.py`` refuses to
touch the row. That contract is correct - automation must not undo a
person's decision - but before this endpoint it was invisible AND permanent:
the user could change the connection setting, watch it not apply to this
conversation, and have no way back.

Scoped to the calling participant, like archive and unarchive: capture
mailbox state is per-participant, never chat-wide.

## Path parameters

- `chat_id` string, uuid, required

## Headers

- `x-impersonate-identity-id` string, nullable

## Response `200`

Successful Response

- CaptureDispositionResetResponse
  - `ok` boolean
  - `changed` boolean

## Other responses

- `422`: Validation Error

---

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