The blocklist prevents Reachkit from sending emails to specific addresses. When someone is on your blocklist, they’re automatically skipped during campaign sending.

Why Use the Blocklist?

Someone asked not to be contacted
You want to avoid emailing competitors, partners, or existing customers
You need to comply with an opt-out request outside the normal unsubscribe flow
You want to protect certain domains from receiving outreach

How It Works

The blocklist is workspace-wide, so it applies to all campaigns. When a campaign is about to send an email, it checks the blocklist first. If the recipient matches a blocklist entry, the email is skipped entirely.

This happens automatically on every send, so you don’t need to manually check each campaign’s lead list.

Adding Entries

Go to Settings > Blocklist to manage your entries. You can add them in two ways:

Manual entry: Paste email addresses into the input field, one per line.

Select from leads: Browse and select from leads already in your workspace.

Removing Entries

Find the entry in the blocklist and remove it. The change takes effect immediately and that address becomes eligible for campaign sends again.

Blocklist via API

On the Scale plan, you can manage your blocklist programmatically:

GET /api/v1/blocklist/check to check if an email is blocked
POST /api/v1/blocklist to add an entry
DELETE /api/v1/blocklist/:id to remove an entry
GET /api/v1/blocklist to list all entries

See the API Documentation article for details.

Blocklist vs. Unsubscribe

These serve different purposes:

Blocklist is controlled by you. You decide who to block.
Unsubscribe is initiated by the recipient when they click an unsubscribe link.

Both prevent future emails, but they come from different actions.