# nv.deleteSavedSearch

Delete one of your Sales Navigator saved searches by its ID.

> The API Reference is also the SDK and CLI reference. Consecutive code fences marked `tab=HTTP`, `tab=Node`, `tab=Python` and `tab=CLI` are the same call on each surface (a fence marked `tab=HTTP,CLI` is the same text for both), and a block between `:::surface <names>` and `:::` applies only to the surfaces it names. Identifiers in the text are written as in Node and in HTTP JSON (camelCase); the Python SDK spells methods, parameters and result attributes in snake_case (`sendMessage` → `send_message`, `reconnectionLink` → `reconnection_link`), while names inside HTTP JSON stay camelCase.

Delete one of your saved lead or account searches in Sales Navigator, by its ID. Only the saved search is deleted; the people and companies it found are not affected.

An active Sales Navigator subscription is required. To find a saved search's ID, call [`nv.retrieveSavedSearches`](/docs/action-nv-retrieve-saved-searches).

:::surface node,python
In the SDK this is the `nvDeleteSavedSearch` method. It takes the parameters below except `label`, which exists only in workflow JSON. It returns no `data`: a failed action comes back in `errors`, with one of the error types below.
:::

:::surface cli
The command is `linkedin navigator saved-searches delete`. Its argument is listed below.
:::

## Constraints

> ⏺️ **Root Start:** allowed.

> ⬆️ **Parent Actions:** N/A.

> ⬇️ **Child Actions:** N/A.

## Parameters

```json tab=HTTP
{
  "actionType": "nv.deleteSavedSearch",
  "label": "deleteHeadsOfSales",
  "savedSearchId": "1900000001"
}
```

```typescript tab=Node
const workflow = await linkedapi.nvDeleteSavedSearch.execute({
  savedSearchId: "1900000001"
});

const { errors } = await linkedapi.nvDeleteSavedSearch.result(workflow.workflowId);
```

```python tab=Python
from linkedapi import NvDeleteSavedSearchParams

workflow = linkedapi.nv_delete_saved_search.execute(
    NvDeleteSavedSearchParams(
        saved_search_id="1900000001",
    )
)

result = linkedapi.nv_delete_saved_search.result(workflow.workflow_id)
```

```bash tab=CLI
linkedin navigator saved-searches delete 1900000001 --json
```

In AI assistants, the MCP tool is `nv_delete_saved_search`. The n8n action is **Delete saved search in Sales Navigator**; the Make module is **Delete Saved Search in Sales Navigator**.

| Parameter | Description |
| --- | --- |
| `label` | Optional label included in workflow completion. |
| `savedSearchId` | Required. ID of one of your saved lead or account searches, as returned in `id` by [`nv.retrieveSavedSearches`](/docs/action-nv-retrieve-saved-searches) or [`nv.createSavedSearch`](/docs/action-nv-create-saved-search). Pass it as a string of digits; a number is rejected. No `type` is needed. |

Invalid parameters are rejected with `invalidWorkflow` before the workflow starts.

:::surface cli
| Arg | Required | Description |
| --- | --- | --- |
| `saved-search-id` | yes | ID of one of your saved lead or account searches |
:::

## Deleting behaviour

- **Exactly the search you name.** The saved search is found by its ID, so another saved search with the same name is never touched.
- **Only your own saved searches.** An ID that is not one of your saved searches fails with `savedSearchNotFound`, and nothing is deleted.
- **Deleting twice.** A saved search that is already deleted is no longer one of yours, so deleting it again fails with `savedSearchNotFound`.
- **English interface only, for now.** This is a current limitation: saved searches work only with an English Sales Navigator interface. On a German, Spanish, French or Portuguese interface, the call fails with `interfaceLanguageNotSupported`.

To save a search, use [`nv.createSavedSearch`](/docs/action-nv-create-saved-search).

## Result options

```json
{
  "actionType": "nv.deleteSavedSearch",
  "label": "deleteHeadsOfSales",
  "success": true
}
```

A successful delete has no `data`. `label` is included only if specified in the action parameters.

## Error result

An unsuccessful action returns `success: false` with an `error` object:

```json
{
  "actionType": "nv.deleteSavedSearch",
  "label": "deleteHeadsOfSales",
  "success": false,
  "error": {
    "type": "savedSearchNotFound",
    "message": "The saved search is not available in Sales Navigator."
  }
}
```

Possible `error.type` values:

- `noSalesNavigator` — the account does not have an active Sales Navigator subscription.
- `savedSearchNotFound` — `savedSearchId` is not one of your saved lead or account searches. This includes a saved search that is already deleted. Nothing is deleted.
- `interfaceLanguageNotSupported` — the account's Sales Navigator interface is German, Spanish, French or Portuguese rather than English. Nothing is deleted; this is a current limitation (see above).
- `unexpectedError` — the saved search could not be deleted, or Linked API could not confirm that it was. It is safe to call again: if the failed call did delete it, the new call fails with `savedSearchNotFound`.