---
title: "Delete a contact"
method: DELETE
path: "/lists/list/{listId}/rows/{leadId}"
tags: ["List contacts"]
---

# Delete a contact

`DELETE /lists/list/{listId}/rows/{leadId}`

## Request

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

Permanently deletes a contact and its company row. The contact can live in the list or in a list linked to it. It is removed from the campaigns that reference it, the list counters are decremented and the campaigns using the list are resynchronized. This cannot be undone. A second call for the same contact returns 404.

Find the `leadId` with the exact lookup of `GET /lists/list/{listId}/rows`. Company-only rows (`co:` ids) cannot be deleted with this route.

## Path parameters

- `listId` string, required
- `leadId` string, required

## Response `200`

Contact deleted.

- ListsSuccess
  - `success` true, required

## Other responses

- `400`: Invalid list id or contact id.
- `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`: List not found (or not yours), or contact not found in this list or its linked lists.
- `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)
