# Remove a lead (/api-reference/leads/removeLead)

## Remove a lead

`DELETE https://app.alienmail.io/api/v1/campaigns/{id}/leads/{email}`

Removes one lead from a campaign and cancels their waiting emails. The emails the campaign already sent them stay in its statistics, and the person stays in your workspace's leads. An `archived` campaign returns 409.

Requires the `LEAD_CAMPAIGN_ENROLL` permission.

Authentication: `Authorization: Bearer <your API key>`

### Parameters

| Name | In | Type | Required | Description |
|---|---|---|---|---|
| `id` | path | integer | yes | The campaign id: the number in the campaign URL in Alienmail, or `id` from the campaign list. An id that is not a campaign of your workspace returns 404. |
| `email` | path | string | yes | The lead email address. Encode it for a URL (`@` as `%40`). Upper and lower case are treated the same. |

### Responses

**200**: The lead was removed.

```json
{
  "removed": true
}
```

**401**: The API key is missing, wrong or revoked, its creator left the workspace or was suspended, or the workspace is archived or deleted.

**403**: The API key's role lacks the permission this endpoint needs.

**404**: The campaign, lead or mailbox was not found in your workspace.

**409**: The campaign, lead or mailbox is in a state that does not allow this. `message` says why.

**429**: More than 120 requests in a minute with this key, or a workspace limit on adding and removing leads.

Errors look like `{ "error": { "code": "not_found", "message": "Campaign not found" } }`. See the Errors page.