---
title: "Delete a list"
method: DELETE
path: "/lists/list/{listId}"
tags: ["Lists"]
---

# Delete a list

`DELETE /lists/list/{listId}`

## Request

- Base URL: `https://api.emelia.io`
- URL: `https://api.emelia.io/lists/list/{listId}`
- Auth: API key in header `Authorization`

Permanently deletes the list, every contact and company row it contains, and its child or linked lists. The deleted list and its contacts are removed from the recipients of your campaigns, which are then resynchronized: deleting a list used as an exclusion list puts the contacts it was excluding back into the campaigns. This cannot be undone.

The call is synchronous: deleting a very large list can take a while.

## Path parameters

- `listId` string, required

## Response `200`

List deleted, with deletion counters.

- ListsDeleteListResult
  - `success` true, required
  - `deletedLists` integer, required: The list plus its linked lists.
  - `deletedContacts` integer, required
  - `deletedCompanies` integer, required
  - `campaignsUpdated` integer, required: Campaigns whose recipients were updated.

## Other responses

- `400`: The list id is not a valid ObjectId.
- `401`: Missing, unknown or disabled API key, or the account of the key no longer exists. Note the body shape: `error` and `code`, not `message`.
- `404`: The list does not exist or belongs to another account.
- `500`: Unexpected server error. `error`, when present, is a raw internal message: do not parse it. Retry later.

---

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