---
title: "Stop lead"
method: DELETE
path: "/v1/leads/{id}"
tags: ["leads"]
---

# Stop lead

`DELETE /v1/leads/{id}`

## Request

- Base URL: `https://api.botdog.co`
- URL: `https://api.botdog.co/v1/leads/{id}`
- Auth: API key in header `x-api-key`

Stop a lead’s campaign sequence. Cancels every remaining step, including a message already waiting out a delay, at any point in the sequence. The lead record is retained; confirm with `stoppedAt` on GET /v1/leads/{id}.

## Path parameters

- `id` string, required

## Response `200`

- StopLeadResponseDto
  - `leadId` string, required: The lead that was stopped
  - `stopped` boolean, required: True when the sequence was torn down and the stop recorded. The request fails with 503 instead of returning false if the sequence could not be stopped, so a 2xx response always means the lead is stopped.

## Other responses

- `401`: Unauthorized. API key is missing or invalid.
- `403`: The key owner has no seat assigned (write endpoints only), the team is on Botdog Managed and so may only read (write endpoints only), or the subscription/plan does not permit this.
- `404`: Lead not found
- `429`: Rate limit exceeded. Retry after cooldown.
- `503`: The sequence could not be stopped and is still running. Nothing was changed — retry.

---

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