---
title: "Stop Segment Endpoint"
method: POST
path: "/api/agent-chat/segments/{segment_id}/stop"
tags: ["Agent Chat"]
---

# Stop Segment Endpoint

`POST /api/agent-chat/segments/{segment_id}/stop`

Reliably STOP a campaign **regardless of status** — unlike /pause, which
is outreach-only and 409s for discovery/searching/review (leaving the
campaign to autonomously search → review → auto-approve → send).

Halts everything that could still cause a send, idempotently:
  1. interrupt any running agent turn (discovery/searching/review/resuming)
     so the lead search / review work stops;
  2. if it's actively sending (outreach) → pause (→ listening) and cancel
     the queued outreach emails;
  3. freeze any pending review's auto-approve countdown so a review segment
     can't tick over into outreach.

Safe to call from any status and repeatedly. Re-enable via /start.

Thin adapter: the orchestration lives in segment_control.stop_campaign
(shared with the public API); this endpoint only translates the cookie
session into an org_id and maps domain errors to HTTP.

## Path parameters

- `segment_id` string, required

## Cookies

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

## Response `200`

Successful Response

- unknown

## 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)