# POST /lists/{id}/contacts/bulk-remove

Part of the SendHeron REST API. Base URL: `https://api.sendheron.com/api/v1`

Remove contacts from a static list.

```http
POST https://api.sendheron.com/api/v1/lists/{id}/contacts/bulk-remove
Authorization: Bearer <YOUR_API_KEY>
```

**Required scopes:** `contacts:write`

**Success status:** `200`

**Rate limit:** 100/min per key, counted against the organization's WRITE ceiling (400/min).

**Path parameters**

| Name | Type | Required | Description |
| --- | --- | --- | --- |
| `id` | uuid | yes | List UUID. |

**Body parameters**

| Name | Type | Required | Description |
| --- | --- | --- | --- |
| `contactIds` | uuid[] | yes | Contact UUIDs to take off the list. One that is not on it, or not in this workspace, is reported in `notFoundIds` rather than refused. Between 1 and 500 per request. |

**Endpoint-specific errors** (beyond the shared error set):

- `400`: `lists.cannotModifyDynamicList`: the list is dynamic, so its members are whoever its rules match. Change the rules instead.

> It is a `POST` because it carries a body, and no `DELETE` in this API takes one. Removing a contact does not touch any enrollment the list started; cancel those through the sequence routes if that is what you mean. A dynamic list is refused (400 `lists.cannotModifyDynamicList`). The response is `{ removedIds, notFoundIds }`, contact ids both, so you can reconcile your own records without a second read: `removedIds` are the ones this call removed, and `notFoundIds` the ones it found nothing to remove for.


---

Rate limits: 100/min per key, counted against the organization's WRITE ceiling (400/min). Both windows are one minute.
