Exclusion lists

We built exclusion lists so the accounts and people you never want to see again — existing customers, competitors, prospects you've already worked — stay out of your searches and audiences. Build a list once, and every search that carries it comes back pre-scrubbed. Creating, filling, and applying lists is free.

There are two kinds, and the difference matters:

How they work

• Add entries by identifier, we do the matching. Every entry is resolved to its canonical company or profile, so URL formatting differences — www. prefixes, trailing paths, country subdomains — all land on the same entity. Entries start filtering shortly after you add them.
• Excluded rows never reach you. Matching results are dropped and back-filled with the next matches, so exclusions don't eat into the result count you asked for.
• Org-wide lists apply themselves. Flag a list isOrganizationWide and every search your organization runs filters through it automatically — no need to pass its ID. Lists without the flag apply only when a request names them.
• Company exclusion runs domain-deep. Excluding a company by its domain keeps everyone working under that domain out of people results, which is usually exactly what "we already have this account" means.
• Deletes are permanent. Removing a list (or an entry) takes effect immediately and can't be undone.

Where they apply

Pass prospectExclusionListIDs / companyExclusionListIDs on:

What you can call

All operations are POST under /v1/exclusions/, mirrored for prospects and companies; each operation name links to its full reference.

Malformed company entries never fail a batch: they're skipped and returned in invalidIdentifiers so you can fix and retry just those. Exclusion endpoints are rate-limited at 120 requests per minute.

In the dashboard

Everything above also lives in the Fiber UI: create Company or People lists, add entries one at a time or by CSV upload (people CSVs need a LinkedIn URL column; company CSVs take Company Name, Company Domain, LinkedIn URL), derive a company list from a prospect list, spawn lists straight from a finished audience, and toggle Excluded org-wide per list. Lists are applied through the Exclusions filter when building an audience. See Using the UI for the walkthrough.

Using it effectively

• Make your do-not-contact list org-wide once instead of passing its ID on every request — it then covers every search anyone in your org runs.
• Pick the right kind: a company list when the whole account is off-limits, a people list when only individuals are.
• Exclusions first. Turn each finished audience into an exclusion list before building the next one, and sequential builds never overlap.
• Expect counts to run high when large lists are attached — the estimate is unfiltered; the results are filtered.

Use cases

• Customer suppression: sync your CRM's account domains into a company list via addCompaniesToExclusionList so active customers never show up in outbound targeting.
• Competitor scrubbing: one org-wide company list keeps competitors (and their employees) out of every teammate's searches.
• Sequential campaigns: after each audience build, create an exclusion list from it — the next build starts from fresh names only.

Credits

Every exclusion operation — creating, adding, reading, removing, deleting — is free. Exclusions change which results come back; they don't change what a search costs. See Billing & credits.