/v1/lists.
Exclusions keep known people or companies, such as existing customers or do-not-contact lists, out of search results.
The API searches first, then removes excluded records before returning results. Matching behavior is unchanged.
Choosing an approach
Supported endpoints
Inline exclusions
Inline exclusions apply only to the request that sends them.People
Useexclude_entity_ids. In people mode it accepts LinkedIn public IDs or LinkedIn profile URLs:
Companies
Company searches useexclude_entity_ids:
- Numeric LinkedIn company IDs
- LinkedIn company URLs
- LinkedIn company slugs
- Exact website domains
Saved exclusion lists
Saved lists are reusable, organization-scoped suppression lists. Each list has anentity_type of person or company, and entity_type defaults to person. A person list can only be used in people search, and a company list only in company search.
Creating a list is asynchronous. A successful request returns 202 Accepted with the list id and status: "pending":
GET /search/exclusion-lists/{list_id} every 10 seconds or slower, and use the list only after status is ready. See List status.
Create from inline IDs
Usesource.type = "entity_ids" for both people and companies.
People:
Create from a CSV upload
Upload the file withPOST /storage/csv/upload (CSV, JSON, or NDJSON), then pass the handle_id it returns as resource_handle_id:
id_column is optional if the API can detect the right column. Column names match without regard to case, spaces, or punctuation, so public_id, publicId, and Public ID are the same column. Without id_column, the API uses the column whose name comes first in this list:
A file with a single column whose header is not recognized is read as a headerless list: its first line is treated as an ID. A file with several columns and none recognized needs
id_column. Values are deduplicated, and a CSV must be UTF-8.
Create from a completed search
Usesource.type = "search_id" to turn a completed search into a reusable list. The source search mode must match the list entity_type: a people search produces a person list, a company search a company list. max_results sets how many top results the list captures, from 1 to 250,000 (the default). name is optional for this source; it defaults to the search’s query and the date.
source can carry its own exclusions, so the list is built from the search results minus another list:
Using a saved list in search
Pass the list ID inexclude_list_ids:
Manage saved lists
GET /search/exclusion-lists returns every list in the organization, most recent first. GET /search/exclusion-lists/{list_id} returns one:
List status
Every list that is not deleted counts toward the active-list limit, including
pending and failed lists. Delete failed lists to free their slots.
Delete a list
DELETE /search/exclusion-lists/{list_id} deletes a list and returns:
Limits
Extended exclusion limits are enabled per organization; contact support@sixtyfour.ai to request them. Lists are immutable: to change one, create a new list and delete the old one.
Pagination
Send exclusions on the first/search/query request. With exclusions, a page can hold fewer rows than page_size, even zero, while has_more is true. See Paginate with cursors.
Deep search
output_mode: "csv", Sixtyfour applies exclusions before producing the CSV. Rows removed by exclude_list_ids are not replaced, so the CSV can hold far fewer than max_results rows. To get up to max_results eligible rows, start the search with output_mode: "query_only" and page with exclusions through POST /search/query, or export it with POST /search/export.
For output_mode: "query_only", the search_id stores the query, not your exclusions. Send them again with the search_id on POST /search/query: