---
title: "Stop watching one person"
method: DELETE
path: "/api/v1/watchlists/{signalId}/profiles/{profileId}"
tags: ["Watchlists"]
---

# Stop watching one person

`DELETE /api/v1/watchlists/{signalId}/profiles/{profileId}`

## Request

- Base URL: `https://api.rodz.io` (the document declares no server; this is the origin it was published from)
- URL: `https://api.rodz.io/api/v1/watchlists/{signalId}/profiles/{profileId}`
- Auth: HTTP bearer

Stop watching one person — for when a champion leaves your ICP, or you are trimming a list down to the accounts you actually sell to.

**Input:** `signalId` and `profileId` (both path parameters). `profileId` is the `id` from `GET /profiles`, not the LinkedIn URL.

**Output:** `204 No Content`.

The entry is archived rather than deleted: its detected-change history stays readable via `GET /changes`, and re-adding the same person later resumes from that history instead of reporting their current role as a brand-new change.

## Path parameters

- `signalId` string, required: Id of the watchlist signal, as returned by the create endpoint.
- `profileId` string, required: Entry id from GET /profiles (not the LinkedIn URL).

## Response `204`

Successful Response

## Other responses

- `400`: The signal exists but watches the other kind of subject
- `404`: No watchlist signal with this id on your account
- `422`: Validation Error
- `429`: Rate limit exceeded. Retry after the number of seconds in the `Retry-After` response header.

---

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