When to use suppression
Add an address to the suppression list in any of the following situations:- Unsubscribe requests — a prospect replies asking to be removed from your outreach or clicks an unsubscribe link.
- Hard bounces — the address is invalid or permanently unreachable and continued sending would harm your domain reputation.
- Legal requests — a contact invokes a right-to-erasure or do-not-contact request under GDPR, CAN-SPAM, or similar regulations.
- Internal domains — your own company’s email domains, to prevent accidental self-sends during testing.
- Competitor domains — addresses you’ve determined should never receive outreach from your workspace.
Add to the suppression list
CallPOST /v1/suppression-list with a JSON body containing an emails array. You can suppress one address or many in a single request.
alreadySuppressed counts addresses that were already on your list before this request — submitting a duplicate address is safe and does not produce an error.
Bulk suppression
Pass multiple addresses in theemails array to suppress them all in a single API call. There is no practical limit to the number of addresses you can include per request.
Suppressed addresses are silently skipped during both enrollment and active sending. They will not appear in error responses or bounce reports — from the API’s perspective, they simply don’t exist as valid recipients in your workspace. This silent-skip behavior ensures suppression works seamlessly without disrupting bulk enrollment workflows.