Skip to main content
Account exclusions prevent Topo from contacting anyone at a company, regardless of which sequences or lists they appear in. Each rule targets a company by domain (for example, competitor.com). Exclusions can be permanent or time-limited via the optional until field, and carry a structured reason code to help you report on and audit your blocklist.
Read endpoints require the account_exclusions:read scope. Create, update, and delete endpoints require account_exclusions:write. Contact exclusions have their own contact_exclusions:* scopes.

Create an exclusion

POST /v1/account-exclusions requires domain and reason. Optional fields include message (a free-form operator note) and until (an RFC 3339 timestamp after which the exclusion expires — omit for a permanent block).

List and manage exclusions

GET /v1/account-exclusions returns every account exclusion in your workspace with the standard pagination envelope. Filter by domain, reason, or creation timestamps. GET /v1/account-exclusions/{exclusion_id} fetches a single rule. PATCH updates mutable fields (reason, message, until). DELETE permanently removes the exclusion. To block a single person without suppressing their entire company, use contact exclusions.

Exclusion reasons

Every account exclusion carries a reason field. Valid values are: