---
title: "Stop all in-flight Tally work in one conversation"
method: POST
path: "/tally/conversations/{id}/stop"
tags: ["Tally"]
---

# Stop all in-flight Tally work in one conversation

`POST /tally/conversations/{id}/stop`

## Request

- Base URL: `https://ledgerhq.pro/api/v1`
- URL: `https://ledgerhq.pro/api/v1/tally/conversations/{id}/stop`
- Auth: one of:
  - HTTP bearer and API key in header `x-organization-id`
  - HTTP bearer and API key in header `x-organization-id`

Cancels every queued and running turn in the conversation and closes its active Bookkeeping Startup goal so background reconciliation cannot resume the work. Explicit program abandon (Cancel from the firm-wide In progress list, or Clear on an ordinary chat before force-new): running workers lose the turn lease immediately, stop at their next tool boundary, and write nothing back. Active Back work / QuickBooks import program claims are released so the process leaves In progress. It is not a pause state — the next message in any conversation starts a fresh turn normally. Cancelling a conversation with no active work is a safe no-op. Clear beside an active import uses /clear-chat instead so the artifact survives.

## Path parameters

- `id` string, uuid, required

## Response `200`

Counts of cancelled turns and closed startup goals

- object
  - `cancelledTurnCount` integer
  - `cancelledGoalCount` integer

## Other responses

- `default`: Error response

---

[API](https://skmtc.dev/ledgerhq-pro/apis/ledgerhq-bookkeeping-api.md) · [All operations](https://skmtc.dev/ledgerhq-pro/apis/ledgerhq-bookkeeping-api/llms.txt) · [OpenAPI document](https://skmtc.dev/ledgerhq-pro/apis/ledgerhq-bookkeeping-api/revisions/9a8269f0a586?raw)
