# List the block list

> The do-not-contact entries the send and research gates enforce, newest first.

Canonical: https://revnu.com/docs/blocklist
Last updated: 2026-11-07

```bash
curl -H "Authorization: Bearer $REVNU_API_TOKEN" "https://revnu.com/api/v1/blocklist?limit=50"
```

## Query

| Parameter | Meaning |
|---|---|
| `limit` | Rows per page, 1 to 200. Default 50. |
| `cursor` | The `nextCursor` from the previous page. |

## Response

`{ "entries": [entry, …], "nextCursor": "…" | null }`. An entry is `{ id, kind, value, reason, source, addedBy, addedAt }`. `kind` is `domain`, `email` or `linkedin`; a `linkedin` value is the profile URL in the form `https://www.linkedin.com/in/<slug>`; `source` says who added it: `customer_import`, `customer` (dashboard), `agent`, `opt_out_reply` (an unsubscribe) or `api`.

## Frequently asked questions

### What does an entry block?

A domain blocks every person at that company and at its subdomains, by email and on LinkedIn. An email blocks one mailbox. A LinkedIn profile blocks one person's connection requests, messages and InMails. Every send asks the block list right before it goes, on both channels: first touches, follow-ups and replies in a conversation that already exists. A lead with a blocked person can't be qualified, and a blocked domain makes research skip the company before spending anything. A LinkedIn person with no saved contact is matched on `linkedin` entries.

### How do I find the id of one entry?

Page through the list with `nextCursor` and match on `value`; there is no search by value. For a sync job, read the whole list once, diff it against your own, then add and remove. See [Add block list entries](https://revnu.com/docs/blocklist-add.md#keep-it-in-sync-with-your-crm).

### Which scope does this need?

`leads:read`. 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.
