# Remove a block list entry

> Unblock one company, mailbox or LinkedIn profile by the id the list returns. Revnu may then contact them again. Unsubscribes can't be removed.

Canonical: https://revnu.com/docs/blocklist-remove
Last updated: 2026-10-18

```bash
curl -X DELETE -H "Authorization: Bearer $REVNU_API_TOKEN" https://revnu.com/api/v1/blocklist/j57…
```

## Response

`{ "removed": entry }`. `404` for an unknown or another account's id. `409` for an address that unsubscribed (`source: opt_out_reply`): it stays blocked. Customer-sync exclusions also return `409` with `customer_relationship`; deleting a block does not remove a customer relationship.

## What removal does

The company or person is no longer blocked from the next research or send decision. Revnu may then find them again and reach out under your normal approvals. Removal doesn't send anything by itself.

## Frequently asked questions

### Is this safe to automate?

Treat it as a deliberate action. A wrong block loses one lead; a wrong unblock can cold-email your own customer. Entries come off through your dashboard (Settings → Agent), this endpoint, or Revnu itself when you name the entry in conversation and confirm. Nobody can remove an unsubscribe or customer-sync exclusion from the dashboard or the API.

### Which scope does this need?

`leads:write`. A token without it gets `403` with `requiredScope` in the body. `GET /me` shows a token's scopes.

### Are responses cached?

No. Every response is `Cache-Control: no-store`, so what you read is current.