Filters and option discovery

The available filters depend on the search type, account permissions, and current catalog. Request capabilities for the complete field contract. Use filter-options to discover values for a catalog-backed field; that lookup does not run a search or charge search or export credits.

curl -X POST "https://ttzqldekaizydrdmirpn.supabase.co/functions/v1/filter-options" \
  -H "Content-Type: application/json" \
  -H "x-searchleads-api-key: sl_live_your_full_api_key_here" \
  -d '{
    "searchType": "people",
    "field": "account.industry",
    "query": "software",
    "limit": 30
  }'

Send an exact readable options[].label in a search request. Existing options[].id values remain accepted for compatibility.

{
  "searchType": "people",
  "filters": { "account.industry": ["Software Development"] },
  "page": 0,
  "size": 25
}

Put free-text fields such as contact.keyword and contact.fullName in textFilters as strings. Put structured includes in filters, and the values you want removed in excludedFilters. Range fields accept min and max; employee count also accepts an array of range objects. Check each field's sendIn, value type, and permitted search types in the capabilities response.

Matching defaults are the same in UI, REST, and MCP. Read each filter's matching.defaultCondition (any or all) and matching.supportsMatchAll. Omitting filterRules.<field>.matchAll inherits that default; explicit JSON false means ANY and true means ALL. String values such as "false" are invalid. See the matching examples.

Option pages contain at most 100 values. REST clamps an oversized positive requested limit to 100; MCP validates its advertised limit of 1–100. Use hasMore and nextCursor to retrieve the remaining values rather than increasing the limit. Query-required fields still require a value search.

Browsing and query-required options

Each field exposes optionDiscovery.mode, minimumQueryLength, pageSizeMax, and starterSample in capabilities and the agent contract. For browseable, omit the query and follow hasMore / nextCursor, keeping field, search type and query unchanged. A starter sample is not the full catalog. For requires_query, send at least two characters; a response with requires_query: true and no options asks for a query and does not mean there are no matching records. not_applicable fields use their documented typed value instead.

Every field also exposes exportVerification.csvKeys, verification, and note. Keys are actual CSV headers. requires_source means exported values alone cannot establish the complete predicate; check the applied query and source data.

Company signals and export mappings

These keys are available only after the current environment's live-index audit succeeds. Check capabilities before sending them. People Search reads the employer's organization fields; Company Search reads the Company index root.

Filter key	Value	Search types	Export key (People / Company)	Elasticsearch source (Company root)
`account.hascio`	`[true]` or `[false]`	People, Company	`companyHasCio` / `hasCio`	`hasCio`
`account.hasciso`	`[true]` or `[false]`	People, Company	`companyHasCiso` / `hasCiso`	`hasCiso`
`account.locationcount`	`{ "min": 1, "max": 10 }`	People, Company	`companyLocationCount` / `locationCount`	`locationCount`
`account.organictraffic`	`{ "min": 0, "max": 10000 }`	People, Company	`companyOrganicTraffic` / `organicTraffic`	`monthlyOrganicTraffic`
`account.paidtraffic`	`{ "min": 0, "max": 10000 }`	People, Company	`companyPaidTraffic` / `paidTraffic`	`monthlyPaidTraffic`
`account.sic`	`["OPTION_ID"]` from option lookup	People, Company	`companySicCodes` / `sicCodes`	`sicCodes`
`account.legaltype`	`["OPTION_ID"]` from option lookup	People, Company	`companyLegalType` / `legalType`	`legalType`
`account.websiteforsale`	`[true]` or `[false]`	People, Company	`companyWebsiteForSale` / `websiteForSale`	`websiteForSale`
`account.websiteworking`	`[true]` or `[false]`	Company	? / `websiteWorking`	`isWebsiteWorking`
`account.linkedinfollowers`	`{ "min": 100 }`	Company	? / `linkedinFollowers`	`linkedinFollowers`
`account.uksic`	`["OPTION_ID"]` from option lookup	Company	? / `ukSicCodes`	`ukSicCodes`

All numeric signal bounds use nonnegative whole numbers and inclusive endpoints; either endpoint may be omitted. Zero is valid. For these new boolean flags, false requires an explicitly stored false value; missing values do not match. CIO/CISO flags describe the company. Codes are strings: preserve leading zeros. Request filter-options for SIC, UK SIC and legal-structure values, without a query to browse, then follow its pagination metadata until complete. Use returned values rather than copying an illustrative code above.

{
  "searchType": "company",
  "filters": {
    "account.hasciso": [true],
    "account.locationcount": { "min": 2 },
    "account.organictraffic": { "min": 1000 }
  },
  "excludedFilters": { "account.websiteforsale": [true] },
  "page": 0,
  "size": 25
}

For SIC, UK SIC and legal structure, replace OPTION_ID with an exact options[].id returned by filter-options. Some upstream UK SIC and legal-structure labels contain a JSON-encoded list, such as ["58190"]. Submit the complete returned label unchanged if using labels; do not extract an individual code from it. Using option IDs avoids nested JSON escaping. The CSV sicCodes and ukSicCodes list columns decode those stored lists into readable codes.

The same JSON filter objects apply to the MCP search tool. Record freshness (updatedAt) is not a supported filter.

App Rating and App Reviews ranges match when either iOS or Google Play satisfies the bounds. Export both platform-specific columns to inspect the matching value. Generic app columns prefer the first available iOS value; see app-store export metrics for keys and mappings.

Value rules

Filter kind	Send in	Shape	Notes
Catalog or exact values	`filters`	Array of strings	Use an exact current `options[].label`; `options[].id` remains accepted.
Free text	`textFilters`	String	Send short terms, not a full prompt. `contact.fullName` uses all-word matching, not exact-name matching.
Numeric range	`filters`	`{ "min": 1, "max": 100 }`	Use the field's units. Employee count also accepts an array of ranges, which are ORed.
Date range	`filters`	`{ "min": "2024-01-01", "max": "2026-01-01" }`	Use ISO calendar dates; numeric date bounds are invalid.
Boolean or presence	`filters`	`["true"]` or `["false"]`	JSON booleans also work. Never send a generic example label.
Department metric	`filters`	`[{ "function": "OPTION_ID", "min": 1, "max": 10 }]`	Replace OPTION_ID with a discovered dimension; a bare range object is invalid.
Exclusion	`excludedFilters`	Field's normal value shape	Use the same key and value rules as the included filter.

Exact domain and LinkedIn filters accept up to 10,000 normalized values per request. Other include and exclude limits come from the live capabilities contract. lookalikeDomains is available only for company searches; use account.domain to target people at known domains. Typed fields such as domains, LinkedIn URLs, websites, and phones do not need catalog discovery.

Role durations use months, founding and education boundaries use years, monetary ranges use USD, and company headcount growth uses percent. Growth accepts a scalar range object, not department metric rows. Read each contract's units and exampleValue before constructing a request. Current job titles accept arbitrary title text, such as ["QA Engineer"]; suggestions do not restrict that field unless the account contract explicitly restricts it.

The legacy email status option has ID VALID and label Valid; both are accepted. Use current option discovery for catalog-backed values. A field may be unavailable to your account even if it appears in a historical integration.

Option pagination

Request up to 100 options per call. When hasMore is true, send nextCursor as cursor with the same searchType, field, and query. A cursor belongs to that lookup and must not be reused for another field or query.

Typeahead fields such as Skills and Education Degree require a query of at least two characters. Continue when hasMore is true even if options is empty. Skills lookup scans up to five underlying document pages per call; a sparse page can still have a valid next cursor. Stop when hasMore is false, or report a bounded lookup as incomplete if your client stops earlier.

For account.metric.employee and account.openroles, call filter-options for that exact field to discover supported dimensions. Send the returned ID or label as function, for example [{ "function": "sales", "min": 1, "max": 10 }] when Sales is returned. Employee Count and Open Roles have different dimension vocabularies. Discovery describes supported inputs, not guaranteed matching records.

If unavailable is true, discovery could not safely serve that catalog. Do not interpret its empty options as zero matching prospects or invent values. Retry later or contact support. An ordinary empty result with unavailable false and hasMore false means that lookup query found no suggestions. For ambiguous locations, use the option's identity metadata as described in search requests.

{
  "searchType": "people",
  "field": "account.industry",
  "query": "software",
  "limit": 100,
  "cursor": "NEXT_CURSOR_FROM_PREVIOUS_RESPONSE"
}

Quick values

These bounded catalogs are convenient copy and paste starting points. For current values and larger catalogs, use the live reference below.

Field	Readable values
`contact.seniority`	C-Team, Director, Manager, Other, Staff, VP
`contact.departmentAndFunction`	Advertising & Marketing; Art, Culture and Creative Professionals; Construction; Customer/Client Service; Education; Engineering; Finance & Accounting; General Business & Management; Healthcare & Human Services; Human Resources; Information Technology; Legal; Manufacturing & Production; Operations; Other; Public Administration & Safety; Purchasing; Research & Development; Sales & Business Development; Science; Supply Chain & Logistics; Writing/Editing
`contact.emailStatus`	Valid
`contact.hasCellphone`	`true`, `false`
`account.funding.lastType`	Angel Round; Convertible Note; Corporate Round; Debt Financing; Equity Crowdfunding; Funding Round; Grant; Initial Coin Offering; Non Equity Assistance; Post-IPO Debt; Post-IPO Equity; Post-IPO Secondary; Pre Seed Round; Private Equity Round; Product Crowdfunding; Secondary Market; Seed Round; Series A; Series B; Series C; Series D; Series E; Series F; Series G; Series H; Series I; Series J; Venture Round

Complete filter reference

The table below is included in the page HTML from the public capability snapshot taken at documentation build time. Search by field name or rule, switch between people and company, and open a field for its value contract, limits, and example. An API key loads your account's current exact contract and allows catalog value lookup. Agents can download the full guide or JSON input contract.

Live filter reference

Explore the current fields, accepted values, and matching rules directly from the API.

Public catalog

Search types

people, company

Max page size

100

Search rate

60/min

Daily allowance

Unlimited

59 of 93 field contracts shown. People and Company permissions and value shapes are listed separately.

account.adspend · Advertising Spend · filters · people

Filter by advertising spend in USD.

Accepted type: Numeric range

Shape: object with grounded min and/or max values

Send a range only when the prompt or campaign strategy gives a real reason for that constraint.

Units: USD

Custom values: Allowed · Include limit: 300 · Exclude limit: 300

Option discovery: No option lookup needed.

CSV mapping: companyAdvertisingSpend. Use these exact CSV header keys to check the corresponding source value; missing values and exclusions follow the documented filter semantics.

Advertising Spend search request

{
  "searchType": "people",
  "filters": {
    "account.adspend": {
      "min": 1000000,
      "max": 10000000
    }
  },
  "page": 0,
  "size": 3
}

Exclude this value

Advertising Spend exclusion request

{
  "searchType": "people",
  "excludedFilters": {
    "account.adspend": {
      "min": 1000000,
      "max": 10000000
    }
  },
  "page": 0,
  "size": 3
}

Matching rules

Same default as the UI: Match ANY selected values. Omit matchAll to inherit this default; use boolean false for ANY or true for ALL where supported.

Advertising Spend search request with rules

{
  "searchType": "people",
  "filters": {
    "account.adspend": {
      "min": 1000000,
      "max": 10000000
    }
  },
  "page": 0,
  "size": 3,
  "filterRules": {
    "account.adspend": {
      "matchAll": false,
      "exclude": false
    }
  }
}

Rule schema (reference only)

{
  "matchAll": {
    "type": "boolean",
    "default": false
  },
  "exclude": {
    "type": "boolean",
    "default": false
  },
  "condition": {
    "enum": [
      "any",
      "all"
    ],
    "default": "any"
  }
}

account.appdownloads · App Downloads · filters · people

Filter by app download count.

Accepted type: Numeric range

Shape: object with grounded min and/or max values

Send a range only when the prompt or campaign strategy gives a real reason for that constraint.

Units: count

Custom values: Allowed · Include limit: 300 · Exclude limit: 300

Option discovery: No option lookup needed.

CSV mapping: companyAppDownloads. Use these exact CSV header keys to check the corresponding source value; missing values and exclusions follow the documented filter semantics.

App Downloads search request

{
  "searchType": "people",
  "filters": {
    "account.appdownloads": {
      "min": 1,
      "max": 100
    }
  },
  "page": 0,
  "size": 3
}

Exclude this value

App Downloads exclusion request

{
  "searchType": "people",
  "excludedFilters": {
    "account.appdownloads": {
      "min": 1,
      "max": 100
    }
  },
  "page": 0,
  "size": 3
}

Matching rules

Same default as the UI: Match ANY selected values. Omit matchAll to inherit this default; use boolean false for ANY or true for ALL where supported.

App Downloads search request with rules

{
  "searchType": "people",
  "filters": {
    "account.appdownloads": {
      "min": 1,
      "max": 100
    }
  },
  "page": 0,
  "size": 3,
  "filterRules": {
    "account.appdownloads": {
      "matchAll": false,
      "exclude": false
    }
  }
}

Rule schema (reference only)

{
  "matchAll": {
    "type": "boolean",
    "default": false
  },
  "exclude": {
    "type": "boolean",
    "default": false
  },
  "condition": {
    "enum": [
      "any",
      "all"
    ],
    "default": "any"
  }
}

account.apppresence · App Presence · filters · people

Filter by app presence.

Accepted type: Yes / No (true / false)

Shape: boolean, "true"/"false", or an array containing one of those values

Send true or false (or the string "true"/"false"). No catalog lookup is needed.

Custom values: Use the documented values · Include limit: 300 · Exclude limit: 300

Option discovery: No option lookup needed.

CSV mapping: companyMobileAppPresence, companyWebAppPresence. Related CSV columns are listed. Matching can span multiple source fields, use fallback values or derived conditions; these columns alone do not prove every predicate.

App Presence search request

{
  "searchType": "people",
  "filters": {
    "account.apppresence": [
      "true"
    ]
  },
  "page": 0,
  "size": 3
}

Exclude this value

App Presence exclusion request

{
  "searchType": "people",
  "excludedFilters": {
    "account.apppresence": [
      "true"
    ]
  },
  "page": 0,
  "size": 3
}

Matching rules

Same default as the UI: Match ANY selected values. Omit matchAll to inherit this default; use boolean false for ANY or true for ALL where supported.

App Presence search request with rules

{
  "searchType": "people",
  "filters": {
    "account.apppresence": [
      "true"
    ]
  },
  "page": 0,
  "size": 3,
  "filterRules": {
    "account.apppresence": {
      "matchAll": false,
      "exclude": false
    }
  }
}

Rule schema (reference only)

{
  "matchAll": {
    "type": "boolean",
    "default": false
  },
  "exclude": {
    "type": "boolean",
    "default": false
  },
  "condition": {
    "enum": [
      "any",
      "all"
    ],
    "default": "any"
  }
}

account.apprating · App Rating · filters · people

Filter by app rating.

Accepted type: Numeric range

Shape: object with grounded min and/or max values

Send a range only when the prompt or campaign strategy gives a real reason for that constraint.

Units: rating

Custom values: Allowed · Include limit: 300 · Exclude limit: 300

Option discovery: No option lookup needed.

CSV mapping: companyAppRating, companyIosAppRating, companyGooglePlayAppRating. Related CSV columns are listed. Matching can span multiple source fields, use fallback values or derived conditions; these columns alone do not prove every predicate.

App Rating search request

{
  "searchType": "people",
  "filters": {
    "account.apprating": {
      "min": 3,
      "max": 5
    }
  },
  "page": 0,
  "size": 3
}

Exclude this value

App Rating exclusion request

{
  "searchType": "people",
  "excludedFilters": {
    "account.apprating": {
      "min": 3,
      "max": 5
    }
  },
  "page": 0,
  "size": 3
}

Matching rules

Same default as the UI: Match ANY selected values. Omit matchAll to inherit this default; use boolean false for ANY or true for ALL where supported.

App Rating search request with rules

{
  "searchType": "people",
  "filters": {
    "account.apprating": {
      "min": 3,
      "max": 5
    }
  },
  "page": 0,
  "size": 3,
  "filterRules": {
    "account.apprating": {
      "matchAll": false,
      "exclude": false
    }
  }
}

Rule schema (reference only)

{
  "matchAll": {
    "type": "boolean",
    "default": false
  },
  "exclude": {
    "type": "boolean",
    "default": false
  },
  "condition": {
    "enum": [
      "any",
      "all"
    ],
    "default": "any"
  }
}

account.appreviews · App Reviews · filters · people

Filter by app review count.

Accepted type: Numeric range

Shape: object with grounded min and/or max values

Send a range only when the prompt or campaign strategy gives a real reason for that constraint.

Units: count

Custom values: Allowed · Include limit: 300 · Exclude limit: 300

Option discovery: No option lookup needed.

CSV mapping: companyAppReviews, companyIosAppReviews, companyGooglePlayAppReviews. Related CSV columns are listed. Matching can span multiple source fields, use fallback values or derived conditions; these columns alone do not prove every predicate.

App Reviews search request

{
  "searchType": "people",
  "filters": {
    "account.appreviews": {
      "min": 1,
      "max": 100
    }
  },
  "page": 0,
  "size": 3
}

Exclude this value

App Reviews exclusion request

{
  "searchType": "people",
  "excludedFilters": {
    "account.appreviews": {
      "min": 1,
      "max": 100
    }
  },
  "page": 0,
  "size": 3
}

Matching rules

Same default as the UI: Match ANY selected values. Omit matchAll to inherit this default; use boolean false for ANY or true for ALL where supported.

App Reviews search request with rules

{
  "searchType": "people",
  "filters": {
    "account.appreviews": {
      "min": 1,
      "max": 100
    }
  },
  "page": 0,
  "size": 3,
  "filterRules": {
    "account.appreviews": {
      "matchAll": false,
      "exclude": false
    }
  }
}

Rule schema (reference only)

{
  "matchAll": {
    "type": "boolean",
    "default": false
  },
  "exclude": {
    "type": "boolean",
    "default": false
  },
  "condition": {
    "enum": [
      "any",
      "all"
    ],
    "default": "any"
  }
}

account.domain · Company Domain · textFilters · people

Filter companies by exact domains.

Accepted type: Exact domain or URL

Shape: string or string[] of exact domains or URLs

Send an exact domain, LinkedIn URL, or website URL. A valid request can return zero matches when the value is not in the dataset.

Custom values: Allowed · Include limit: 10000 · Exclude limit: 10000

Option discovery: No option lookup needed.

CSV mapping: companyDomain, companyWebsite. Use these exact CSV header keys to check the corresponding source value; missing values and exclusions follow the documented filter semantics.

Company Domain search request

{
  "searchType": "people",
  "textFilters": {
    "account.domain": "example.com"
  },
  "page": 0,
  "size": 3
}

Exclude this value

Company Domain exclusion request

{
  "searchType": "people",
  "excludedFilters": {
    "account.domain": "example.com"
  },
  "page": 0,
  "size": 3
}

Matching rules

Same default as the UI: Match ANY selected values. Omit matchAll to inherit this default; use boolean false for ANY or true for ALL where supported.

Company Domain search request with rules

{
  "searchType": "people",
  "textFilters": {
    "account.domain": "example.com"
  },
  "page": 0,
  "size": 3,
  "filterRules": {
    "account.domain": {
      "matchAll": false,
      "exclude": false
    }
  }
}

Rule schema (reference only)

{
  "matchAll": {
    "type": "boolean",
    "default": false
  },
  "exclude": {
    "type": "boolean",
    "default": false
  },
  "condition": {
    "enum": [
      "any",
      "all"
    ],
    "default": "any"
  }
}

account.employeesize · Employee Count · filters · people

Filter companies by employee count range.

Accepted type: Numeric range

Shape: one object with min and/or max, or an array of those range objects

A single range object remains supported. Multiple Employee Count ranges are ORed; use grounded non-negative integer boundaries.

Units: count

Custom values: Allowed · Include limit: 300 · Exclude limit: 300

Option discovery: No option lookup needed.

CSV mapping: companyEmployees. Use these exact CSV header keys to check the corresponding source value; missing values and exclusions follow the documented filter semantics.

Employee Count search request

{
  "searchType": "people",
  "filters": {
    "account.employeesize": {
      "min": 1,
      "max": 100
    }
  },
  "page": 0,
  "size": 3
}

Exclude this value

Employee Count exclusion request

{
  "searchType": "people",
  "excludedFilters": {
    "account.employeesize": {
      "min": 1,
      "max": 100
    }
  },
  "page": 0,
  "size": 3
}

Matching rules

Same default as the UI: Match ANY selected values. Omit matchAll to inherit this default; use boolean false for ANY or true for ALL where supported.

Employee Count search request with rules

{
  "searchType": "people",
  "filters": {
    "account.employeesize": {
      "min": 1,
      "max": 100
    }
  },
  "page": 0,
  "size": 3,
  "filterRules": {
    "account.employeesize": {
      "matchAll": false,
      "exclude": false
    }
  }
}

Rule schema (reference only)

{
  "matchAll": {
    "type": "boolean",
    "default": false
  },
  "exclude": {
    "type": "boolean",
    "default": false
  },
  "condition": {
    "enum": [
      "any",
      "all"
    ],
    "default": "any"
  }
}

account.foundedyear · Founded Year · filters · people

Filter by company founding year.

Accepted type: Numeric range

Shape: object with grounded min and/or max values

Send a range only when the prompt or campaign strategy gives a real reason for that constraint.

Units: year

Custom values: Allowed · Include limit: 300 · Exclude limit: 300

Option discovery: No option lookup needed.

CSV mapping: companyFoundedYear. Use these exact CSV header keys to check the corresponding source value; missing values and exclusions follow the documented filter semantics.

Founded Year search request

{
  "searchType": "people",
  "filters": {
    "account.foundedyear": {
      "min": 2010,
      "max": 2025
    }
  },
  "page": 0,
  "size": 3
}

Exclude this value

Founded Year exclusion request

{
  "searchType": "people",
  "excludedFilters": {
    "account.foundedyear": {
      "min": 2010,
      "max": 2025
    }
  },
  "page": 0,
  "size": 3
}

Matching rules

Same default as the UI: Match ANY selected values. Omit matchAll to inherit this default; use boolean false for ANY or true for ALL where supported.

Founded Year search request with rules

{
  "searchType": "people",
  "filters": {
    "account.foundedyear": {
      "min": 2010,
      "max": 2025
    }
  },
  "page": 0,
  "size": 3,
  "filterRules": {
    "account.foundedyear": {
      "matchAll": false,
      "exclude": false
    }
  }
}

Rule schema (reference only)

{
  "matchAll": {
    "type": "boolean",
    "default": false
  },
  "exclude": {
    "type": "boolean",
    "default": false
  },
  "condition": {
    "enum": [
      "any",
      "all"
    ],
    "default": "any"
  }
}

account.funding.available · Has Funding Data · filters · people

Filter by whether funding data exists.

Accepted type: Yes / No (true / false)

Shape: boolean, "true"/"false", or an array containing one of those values

Send true or false (or the string "true"/"false"). No catalog lookup is needed.

Custom values: Use the documented values · Include limit: 1 · Exclude limit: 1

Option discovery: No option lookup needed.

CSV mapping: companyLastFundingType. Related CSV columns are listed. Matching can span multiple source fields, use fallback values or derived conditions; these columns alone do not prove every predicate.

Has Funding Data search request

{
  "searchType": "people",
  "filters": {
    "account.funding.available": [
      "true"
    ]
  },
  "page": 0,
  "size": 3
}

Exclude this value

Has Funding Data exclusion request

{
  "searchType": "people",
  "excludedFilters": {
    "account.funding.available": [
      "true"
    ]
  },
  "page": 0,
  "size": 3
}

Matching rules

Same default as the UI: Match ANY selected values. Omit matchAll to inherit this default; use boolean false for ANY or true for ALL where supported.

Has Funding Data search request with rules

{
  "searchType": "people",
  "filters": {
    "account.funding.available": [
      "true"
    ]
  },
  "page": 0,
  "size": 3,
  "filterRules": {
    "account.funding.available": {
      "matchAll": false,
      "exclude": false
    }
  }
}

Rule schema (reference only)

{
  "matchAll": {
    "type": "boolean",
    "default": false
  },
  "exclude": {
    "type": "boolean",
    "default": false
  },
  "condition": {
    "enum": [
      "any",
      "all"
    ],
    "default": "any"
  }
}

account.funding.investorcount · Investor Count · filters · people

Filter by funding investor count.

Accepted type: Numeric range

Shape: object with grounded min and/or max values

Send a range only when the prompt or campaign strategy gives a real reason for that constraint.

Units: count

Custom values: Allowed · Include limit: 20 · Exclude limit: 20

Option discovery: No option lookup needed.

CSV mapping: companyInvestorCount. Use these exact CSV header keys to check the corresponding source value; missing values and exclusions follow the documented filter semantics.

Investor Count search request

{
  "searchType": "people",
  "filters": {
    "account.funding.investorcount": {
      "min": 1,
      "max": 100
    }
  },
  "page": 0,
  "size": 3
}

Exclude this value

Investor Count exclusion request

{
  "searchType": "people",
  "excludedFilters": {
    "account.funding.investorcount": {
      "min": 1,
      "max": 100
    }
  },
  "page": 0,
  "size": 3
}

Matching rules

Same default as the UI: Match ANY selected values. Omit matchAll to inherit this default; use boolean false for ANY or true for ALL where supported.

Investor Count search request with rules

{
  "searchType": "people",
  "filters": {
    "account.funding.investorcount": {
      "min": 1,
      "max": 100
    }
  },
  "page": 0,
  "size": 3,
  "filterRules": {
    "account.funding.investorcount": {
      "matchAll": false,
      "exclude": false
    }
  }
}

Rule schema (reference only)

{
  "matchAll": {
    "type": "boolean",
    "default": false
  },
  "exclude": {
    "type": "boolean",
    "default": false
  },
  "condition": {
    "enum": [
      "any",
      "all"
    ],
    "default": "any"
  }
}

account.funding.lastamount · Last Funding Amount · filters · people

Filter by the latest funding round amount.

Accepted type: Numeric range

Shape: object with grounded min and/or max values

Send a range only when the prompt or campaign strategy gives a real reason for that constraint.

Units: USD

Custom values: Allowed · Include limit: 20 · Exclude limit: 20

Option discovery: No option lookup needed.

CSV mapping: companyLastFundingAmount. Use these exact CSV header keys to check the corresponding source value; missing values and exclusions follow the documented filter semantics.

Last Funding Amount search request

{
  "searchType": "people",
  "filters": {
    "account.funding.lastamount": {
      "min": 1000000,
      "max": 10000000
    }
  },
  "page": 0,
  "size": 3
}

Exclude this value

Last Funding Amount exclusion request

{
  "searchType": "people",
  "excludedFilters": {
    "account.funding.lastamount": {
      "min": 1000000,
      "max": 10000000
    }
  },
  "page": 0,
  "size": 3
}

Matching rules

Same default as the UI: Match ANY selected values. Omit matchAll to inherit this default; use boolean false for ANY or true for ALL where supported.

Last Funding Amount search request with rules

{
  "searchType": "people",
  "filters": {
    "account.funding.lastamount": {
      "min": 1000000,
      "max": 10000000
    }
  },
  "page": 0,
  "size": 3,
  "filterRules": {
    "account.funding.lastamount": {
      "matchAll": false,
      "exclude": false
    }
  }
}

Rule schema (reference only)

{
  "matchAll": {
    "type": "boolean",
    "default": false
  },
  "exclude": {
    "type": "boolean",
    "default": false
  },
  "condition": {
    "enum": [
      "any",
      "all"
    ],
    "default": "any"
  }
}

account.funding.lastdate · Last Funding Date · filters · people

Filter by latest funding date.

Accepted type: Calendar date range

Shape: object with ISO 8601 min and/or max dates (YYYY-MM-DD)

Send ISO 8601 calendar dates as min and/or max; do not use numeric timestamps.

Units: ISO 8601 date (YYYY-MM-DD)

Custom values: Allowed · Include limit: 20 · Exclude limit: 20

Option discovery: No option lookup needed.

CSV mapping: companyLastFundingDate. Use these exact CSV header keys to check the corresponding source value; missing values and exclusions follow the documented filter semantics.

Last Funding Date search request

{
  "searchType": "people",
  "filters": {
    "account.funding.lastdate": {
      "min": "2024-01-01",
      "max": "2026-01-01"
    }
  },
  "page": 0,
  "size": 3
}

Exclude this value

Last Funding Date exclusion request

{
  "searchType": "people",
  "excludedFilters": {
    "account.funding.lastdate": {
      "min": "2024-01-01",
      "max": "2026-01-01"
    }
  },
  "page": 0,
  "size": 3
}

Matching rules

Same default as the UI: Match ANY selected values. Omit matchAll to inherit this default; use boolean false for ANY or true for ALL where supported.

Last Funding Date search request with rules

{
  "searchType": "people",
  "filters": {
    "account.funding.lastdate": {
      "min": "2024-01-01",
      "max": "2026-01-01"
    }
  },
  "page": 0,
  "size": 3,
  "filterRules": {
    "account.funding.lastdate": {
      "matchAll": false,
      "exclude": false
    }
  }
}

Rule schema (reference only)

{
  "matchAll": {
    "type": "boolean",
    "default": false
  },
  "exclude": {
    "type": "boolean",
    "default": false
  },
  "condition": {
    "enum": [
      "any",
      "all"
    ],
    "default": "any"
  }
}

account.funding.lasttype · Last Funding Type · filters · people

Filter by the latest funding round type.

Accepted type: Select exact catalog values

Shape: string[] of exact current option IDs or readable labels

Call the filter-options option lookup, then submit exact options[].id or options[].label values. Do not invent catalog values.

Custom values: Use the documented values · Include limit: 50 · Exclude limit: 50

Option discovery: Browse without a query; follow nextCursor while hasMore is true.

CSV mapping: companyLastFundingType. Use these exact CSV header keys to check the corresponding source value; missing values and exclusions follow the documented filter semantics.

Select a returned catalog value to generate an exact search request. No catalog value is assumed.

Last Funding Type lookup request

{
  "searchType": "people",
  "field": "account.funding.lasttype",
  "limit": 100
}

Matching rules

Same default as the UI: Match ANY selected values. Omit matchAll to inherit this default; use boolean false for ANY or true for ALL where supported.

Last Funding Type rule values fragment

{
  "filterRules": {
    "account.funding.lasttype": {
      "matchAll": false,
      "exclude": false
    }
  }
}

Merge this filterRules fragment into the search request generated after selecting a catalog value.

Rule schema (reference only)

{
  "matchAll": {
    "type": "boolean",
    "default": false
  },
  "exclude": {
    "type": "boolean",
    "default": false
  },
  "condition": {
    "enum": [
      "any",
      "all"
    ],
    "default": "any"
  }
}

account.funding.leadinvestors · Lead Investors · filters · people

Filter by lead investors.

Accepted type: Select exact catalog values

Shape: string[] of exact current option IDs or readable labels

Call the filter-options option lookup, then submit exact options[].id or options[].label values. Do not invent catalog values.

Custom values: Use the documented values · Include limit: 100 · Exclude limit: 100

Option discovery: Blank lookup returns a starter sample. Type a query for broader discovery.

CSV mapping: companyLeadInvestors. Use these exact CSV header keys to check the corresponding source value; missing values and exclusions follow the documented filter semantics.

Select a returned catalog value to generate an exact search request. No catalog value is assumed.

Lead Investors lookup request

{
  "searchType": "people",
  "field": "account.funding.leadinvestors",
  "limit": 100
}

Matching rules

Same default as the UI: Match ANY selected values. Omit matchAll to inherit this default; use boolean false for ANY or true for ALL where supported.

Lead Investors rule values fragment

{
  "filterRules": {
    "account.funding.leadinvestors": {
      "matchAll": false,
      "exclude": false
    }
  }
}

Merge this filterRules fragment into the search request generated after selecting a catalog value.

Rule schema (reference only)

{
  "matchAll": {
    "type": "boolean",
    "default": false
  },
  "exclude": {
    "type": "boolean",
    "default": false
  },
  "condition": {
    "enum": [
      "any",
      "all"
    ],
    "default": "any"
  }
}

account.funding.totalamount · Total Funding · filters · people

Filter by total funding amount.

Accepted type: Numeric range

Shape: object with grounded min and/or max values

Send a range only when the prompt or campaign strategy gives a real reason for that constraint.

Units: USD

Custom values: Allowed · Include limit: 20 · Exclude limit: 20

Option discovery: No option lookup needed.

CSV mapping: companyTotalFunding. Use these exact CSV header keys to check the corresponding source value; missing values and exclusions follow the documented filter semantics.

Total Funding search request

{
  "searchType": "people",
  "filters": {
    "account.funding.totalamount": {
      "min": 1000000,
      "max": 10000000
    }
  },
  "page": 0,
  "size": 3
}

Exclude this value

Total Funding exclusion request

{
  "searchType": "people",
  "excludedFilters": {
    "account.funding.totalamount": {
      "min": 1000000,
      "max": 10000000
    }
  },
  "page": 0,
  "size": 3
}

Matching rules

Same default as the UI: Match ANY selected values. Omit matchAll to inherit this default; use boolean false for ANY or true for ALL where supported.

Total Funding search request with rules

{
  "searchType": "people",
  "filters": {
    "account.funding.totalamount": {
      "min": 1000000,
      "max": 10000000
    }
  },
  "page": 0,
  "size": 3,
  "filterRules": {
    "account.funding.totalamount": {
      "matchAll": false,
      "exclude": false
    }
  }
}

Rule schema (reference only)

{
  "matchAll": {
    "type": "boolean",
    "default": false
  },
  "exclude": {
    "type": "boolean",
    "default": false
  },
  "condition": {
    "enum": [
      "any",
      "all"
    ],
    "default": "any"
  }
}

account.hascio · Has CIO · filters · people

Filter by whether the company has a CIO. This describes the employer in People Search.

Accepted type: Yes / No (true / false)

Shape: boolean, "true"/"false", or an array containing one of those values

Send true or false (or the string "true"/"false"). No catalog lookup is needed.

No matches explicitly stored false values. Unknown values are separate; exclude true to also include unknown values.

Custom values: Use the documented values · Include limit: 300 · Exclude limit: 300

Option discovery: No option lookup needed.

CSV mapping: companyHasCio. Use these exact CSV header keys to check the corresponding source value; missing values and exclusions follow the documented filter semantics.

Has CIO search request

{
  "searchType": "people",
  "filters": {
    "account.hascio": [
      "true"
    ]
  },
  "page": 0,
  "size": 3
}

Exclude this value

Has CIO exclusion request

{
  "searchType": "people",
  "excludedFilters": {
    "account.hascio": [
      "true"
    ]
  },
  "page": 0,
  "size": 3
}

Matching rules

Same default as the UI: Match ANY selected values. Omit matchAll to inherit this default; use boolean false for ANY or true for ALL where supported.

Has CIO search request with rules

{
  "searchType": "people",
  "filters": {
    "account.hascio": [
      "true"
    ]
  },
  "page": 0,
  "size": 3,
  "filterRules": {
    "account.hascio": {
      "matchAll": false,
      "exclude": false
    }
  }
}

Rule schema (reference only)

{
  "matchAll": {
    "type": "boolean",
    "default": false
  },
  "exclude": {
    "type": "boolean",
    "default": false
  },
  "condition": {
    "enum": [
      "any",
      "all"
    ],
    "default": "any"
  }
}

account.hasciso · Has CISO · filters · people

Filter by whether the company has a CISO. This describes the employer in People Search.

Accepted type: Yes / No (true / false)

Shape: boolean, "true"/"false", or an array containing one of those values

Send true or false (or the string "true"/"false"). No catalog lookup is needed.

No matches explicitly stored false values. Unknown values are separate; exclude true to also include unknown values.

Custom values: Use the documented values · Include limit: 300 · Exclude limit: 300

Option discovery: No option lookup needed.

CSV mapping: companyHasCiso. Use these exact CSV header keys to check the corresponding source value; missing values and exclusions follow the documented filter semantics.

Has CISO search request

{
  "searchType": "people",
  "filters": {
    "account.hasciso": [
      "true"
    ]
  },
  "page": 0,
  "size": 3
}

Exclude this value

Has CISO exclusion request

{
  "searchType": "people",
  "excludedFilters": {
    "account.hasciso": [
      "true"
    ]
  },
  "page": 0,
  "size": 3
}

Matching rules

Same default as the UI: Match ANY selected values. Omit matchAll to inherit this default; use boolean false for ANY or true for ALL where supported.

Has CISO search request with rules

{
  "searchType": "people",
  "filters": {
    "account.hasciso": [
      "true"
    ]
  },
  "page": 0,
  "size": 3,
  "filterRules": {
    "account.hasciso": {
      "matchAll": false,
      "exclude": false
    }
  }
}

Rule schema (reference only)

{
  "matchAll": {
    "type": "boolean",
    "default": false
  },
  "exclude": {
    "type": "boolean",
    "default": false
  },
  "condition": {
    "enum": [
      "any",
      "all"
    ],
    "default": "any"
  }
}

account.hiring · Hiring & Open Roles · filters · people

Select hiring departments from the current catalog.

Accepted type: Select exact catalog values

Shape: string[] of exact current option IDs or readable labels

Call the filter-options option lookup, then submit exact options[].id or options[].label values. Do not invent catalog values.

Custom values: Use the documented values · Include limit: 300 · Exclude limit: 300

Option discovery: Browse without a query; follow nextCursor while hasMore is true.

CSV mapping: companyHiringDepartments. Use these exact CSV header keys to check the corresponding source value; missing values and exclusions follow the documented filter semantics.

Select a returned catalog value to generate an exact search request. No catalog value is assumed.

Hiring & Open Roles lookup request

{
  "searchType": "people",
  "field": "account.hiring",
  "limit": 100
}

Matching rules

Same default as the UI: Match ANY selected values. Omit matchAll to inherit this default; use boolean false for ANY or true for ALL where supported.

Hiring & Open Roles rule values fragment

{
  "filterRules": {
    "account.hiring": {
      "matchAll": false,
      "exclude": false
    }
  }
}

Merge this filterRules fragment into the search request generated after selecting a catalog value.

Rule schema (reference only)

{
  "matchAll": {
    "type": "boolean",
    "default": false
  },
  "exclude": {
    "type": "boolean",
    "default": false
  },
  "condition": {
    "enum": [
      "any",
      "all"
    ],
    "default": "any"
  }
}

account.industry · Industry · filters · people

Filter companies by industry.

Accepted type: Select exact catalog values

Shape: string[] of exact current option IDs or readable labels

Call the filter-options option lookup, then submit exact options[].id or options[].label values. Do not invent catalog values.

Custom values: Use the documented values · Include limit: 300 · Exclude limit: 300

Option discovery: Browse without a query; follow nextCursor while hasMore is true.

CSV mapping: companyIndustry. Use these exact CSV header keys to check the corresponding source value; missing values and exclusions follow the documented filter semantics.

Select a returned catalog value to generate an exact search request. No catalog value is assumed.

Industry lookup request

{
  "searchType": "people",
  "field": "account.industry",
  "limit": 100
}

Matching rules

Same default as the UI: Match ANY selected values. Omit matchAll to inherit this default; use boolean false for ANY or true for ALL where supported.

Industry rule values fragment

{
  "filterRules": {
    "account.industry": {
      "matchAll": false,
      "exclude": false
    }
  }
}

Merge this filterRules fragment into the search request generated after selecting a catalog value.

Rule schema (reference only)

{
  "matchAll": {
    "type": "boolean",
    "default": false
  },
  "exclude": {
    "type": "boolean",
    "default": false
  },
  "condition": {
    "enum": [
      "any",
      "all"
    ],
    "default": "any"
  }
}

account.keyword · Account Keywords · textFilters · people

Search supported company sources for keywords.

Accepted type: Text values

Shape: string or string[] of short keyword terms

Custom values are allowed, but keep them concise buyer-side terms. Do not send full prompts or sentences.

Custom values: Allowed · Include limit: 300 · Exclude limit: 300

Option discovery: No option lookup needed.

CSV mapping: company, companyDescription, companyIndustry, companyTechnologies, companyKeywords. Related CSV columns are listed. Matching can span multiple source fields, use fallback values or derived conditions; these columns alone do not prove every predicate.

Account Keywords search request

{
  "searchType": "people",
  "textFilters": {
    "account.keyword": "outbound sales"
  },
  "page": 0,
  "size": 3
}

Exclude this value

Account Keywords exclusion request

{
  "searchType": "people",
  "excludedFilters": {
    "account.keyword": "outbound sales"
  },
  "page": 0,
  "size": 3
}

Matching rules

Same default as the UI: Match ANY selected values. Omit matchAll to inherit this default; use boolean false for ANY or true for ALL where supported.

Account Keywords search request with rules

{
  "searchType": "people",
  "textFilters": {
    "account.keyword": "outbound sales"
  },
  "page": 0,
  "size": 3,
  "filterRules": {
    "account.keyword": {
      "matchAll": false,
      "exclude": false,
      "mode": "SMART"
    }
  }
}

Rule schema (reference only)

{
  "matchAll": {
    "type": "boolean",
    "default": false
  },
  "exclude": {
    "type": "boolean",
    "default": false
  },
  "mode": {
    "enum": [
      "SMART",
      "WORD",
      "STRICT"
    ],
    "default": "SMART"
  },
  "condition": {
    "enum": [
      "any",
      "all"
    ],
    "default": "any"
  },
  "sources": {
    "type": "array",
    "items": {
      "enum": [
        "NAME",
        "DESCRIPTION",
        "SPECIALTIES",
        "INDUSTRY",
        "TECHNOLOGIES"
      ]
    }
  },
  "includeSources": {
    "type": "array",
    "items": {
      "enum": [
        "NAME",
        "DESCRIPTION",
        "SPECIALTIES",
        "INDUSTRY",
        "TECHNOLOGIES"
      ]
    }
  },
  "excludeSources": {
    "type": "array",
    "items": {
      "enum": [
        "NAME",
        "DESCRIPTION",
        "SPECIALTIES",
        "INDUSTRY",
        "TECHNOLOGIES"
      ]
    }
  }
}

account.legaltype · Legal Structure · filters · people

Filter by exact legal-structure values from the current catalog.

Accepted type: Select exact catalog values

Shape: string[] of exact current option IDs or readable labels

Call the filter-options option lookup, then submit exact options[].id or options[].label values. Do not invent catalog values.

Custom values: Use the documented values · Include limit: 300 · Exclude limit: 300

Option discovery: Browse without a query; follow nextCursor while hasMore is true.

CSV mapping: companyLegalType. Use these exact CSV header keys to check the corresponding source value; missing values and exclusions follow the documented filter semantics.

Select a returned catalog value to generate an exact search request. No catalog value is assumed.

Legal Structure lookup request

{
  "searchType": "people",
  "field": "account.legaltype",
  "limit": 100
}

Matching rules

Same default as the UI: Match ANY selected values. Omit matchAll to inherit this default; use boolean false for ANY or true for ALL where supported.

Legal Structure rule values fragment

{
  "filterRules": {
    "account.legaltype": {
      "matchAll": false,
      "exclude": false
    }
  }
}

Merge this filterRules fragment into the search request generated after selecting a catalog value.

Rule schema (reference only)

{
  "matchAll": {
    "type": "boolean",
    "default": false
  },
  "exclude": {
    "type": "boolean",
    "default": false
  },
  "condition": {
    "enum": [
      "any",
      "all"
    ],
    "default": "any"
  }
}

account.linkedin · Company LinkedIn · textFilters · people

Filter by LinkedIn company page URL.

Accepted type: Exact domain or URL

Shape: string or string[] of exact domains or URLs

Send an exact domain, LinkedIn URL, or website URL. A valid request can return zero matches when the value is not in the dataset.

Custom values: Allowed · Include limit: 10000 · Exclude limit: 10000

Option discovery: No option lookup needed.

CSV mapping: companyLinkedin. Use these exact CSV header keys to check the corresponding source value; missing values and exclusions follow the documented filter semantics.

Company LinkedIn search request

{
  "searchType": "people",
  "textFilters": {
    "account.linkedin": "https://www.linkedin.com/company/example"
  },
  "page": 0,
  "size": 3
}

Exclude this value

Company LinkedIn exclusion request

{
  "searchType": "people",
  "excludedFilters": {
    "account.linkedin": "https://www.linkedin.com/company/example"
  },
  "page": 0,
  "size": 3
}

Matching rules

Same default as the UI: Match ANY selected values. Omit matchAll to inherit this default; use boolean false for ANY or true for ALL where supported.

Company LinkedIn search request with rules

{
  "searchType": "people",
  "textFilters": {
    "account.linkedin": "https://www.linkedin.com/company/example"
  },
  "page": 0,
  "size": 3,
  "filterRules": {
    "account.linkedin": {
      "matchAll": false,
      "exclude": false
    }
  }
}

Rule schema (reference only)

{
  "matchAll": {
    "type": "boolean",
    "default": false
  },
  "exclude": {
    "type": "boolean",
    "default": false
  },
  "condition": {
    "enum": [
      "any",
      "all"
    ],
    "default": "any"
  }
}

account.location · Company Location · filters · people

Filter companies by headquarters location, region, state, or country.

Accepted type: Select exact catalog values

Shape: string[] of exact current option IDs or readable labels

Call the filter-options option lookup, then submit exact options[].id or options[].label values. Do not invent catalog values.

Custom values: Use the documented values · Include limit: 300 · Exclude limit: 300

Option discovery: Enter at least 2 characters; blank lookup is not a complete catalog.

CSV mapping: companyLocation. Related CSV columns are listed. Matching can span multiple source fields, use fallback values or derived conditions; these columns alone do not prove every predicate.

Company Location search request

{
  "searchType": "people",
  "filters": {
    "account.location": [
      "United States"
    ]
  },
  "page": 0,
  "size": 3
}

Exclude this value

Company Location exclusion request

{
  "searchType": "people",
  "excludedFilters": {
    "account.location": [
      "United States"
    ]
  },
  "page": 0,
  "size": 3
}

Company Location lookup request

{
  "searchType": "people",
  "field": "account.location",
  "limit": 100
}

Matching rules

Same default as the UI: Match ANY selected values. Omit matchAll to inherit this default; use boolean false for ANY or true for ALL where supported.

Company Location search request with rules

{
  "searchType": "people",
  "filters": {
    "account.location": [
      "United States"
    ]
  },
  "page": 0,
  "size": 3,
  "filterRules": {
    "account.location": {
      "matchAll": false,
      "exclude": false
    }
  }
}

Rule schema (reference only)

{
  "matchAll": {
    "type": "boolean",
    "default": false
  },
  "exclude": {
    "type": "boolean",
    "default": false
  },
  "condition": {
    "enum": [
      "any",
      "all"
    ],
    "default": "any"
  }
}

account.locationcount · Number of Locations · filters · people

Filter by the number of company locations.

Accepted type: Numeric range

Shape: object with grounded min and/or max values

Send a range only when the prompt or campaign strategy gives a real reason for that constraint.

Units: count

Numeric bounds: whole numbers, minimum 0, inclusive endpoints. Zero is preserved.

Custom values: Allowed · Include limit: 300 · Exclude limit: 300

Option discovery: No option lookup needed.

CSV mapping: companyLocationCount. Use these exact CSV header keys to check the corresponding source value; missing values and exclusions follow the documented filter semantics.

Number of Locations search request

{
  "searchType": "people",
  "filters": {
    "account.locationcount": {
      "min": 1,
      "max": 100
    }
  },
  "page": 0,
  "size": 3
}

Exclude this value

Number of Locations exclusion request

{
  "searchType": "people",
  "excludedFilters": {
    "account.locationcount": {
      "min": 1,
      "max": 100
    }
  },
  "page": 0,
  "size": 3
}

Matching rules

Same default as the UI: Match ANY selected values. Omit matchAll to inherit this default; use boolean false for ANY or true for ALL where supported.

Number of Locations search request with rules

{
  "searchType": "people",
  "filters": {
    "account.locationcount": {
      "min": 1,
      "max": 100
    }
  },
  "page": 0,
  "size": 3,
  "filterRules": {
    "account.locationcount": {
      "matchAll": false,
      "exclude": false
    }
  }
}

Rule schema (reference only)

{
  "matchAll": {
    "type": "boolean",
    "default": false
  },
  "exclude": {
    "type": "boolean",
    "default": false
  },
  "condition": {
    "enum": [
      "any",
      "all"
    ],
    "default": "any"
  }
}

account.metric.growth · Headcount Growth · filters · people

Filter by company headcount growth percentage.

Accepted type: Numeric range

Shape: object with grounded min and/or max values

Send a range only when the prompt or campaign strategy gives a real reason for that constraint.

Units: percent

Custom values: Allowed · Include limit: 300 · Exclude limit: 300

Option discovery: No option lookup needed.

CSV mapping: companyHeadcountGrowth. Use these exact CSV header keys to check the corresponding source value; missing values and exclusions follow the documented filter semantics.

Headcount Growth search request

{
  "searchType": "people",
  "filters": {
    "account.metric.growth": {
      "min": 10,
      "max": 50
    }
  },
  "page": 0,
  "size": 3
}

Exclude this value

Headcount Growth exclusion request

{
  "searchType": "people",
  "excludedFilters": {
    "account.metric.growth": {
      "min": 10,
      "max": 50
    }
  },
  "page": 0,
  "size": 3
}

Matching rules

Same default as the UI: Match ANY selected values. Omit matchAll to inherit this default; use boolean false for ANY or true for ALL where supported.

Headcount Growth search request with rules

{
  "searchType": "people",
  "filters": {
    "account.metric.growth": {
      "min": 10,
      "max": 50
    }
  },
  "page": 0,
  "size": 3,
  "filterRules": {
    "account.metric.growth": {
      "min": 10,
      "max": 50
    }
  }
}

Rule schema (reference only)

{
  "min": {
    "type": "number"
  },
  "max": {
    "type": "number"
  }
}

account.naics · NAICS · filters · people

Filter by exact NAICS values from the current catalog.

Accepted type: Select exact catalog values

Shape: string[] of exact current option IDs or readable labels

Call the filter-options option lookup, then submit exact options[].id or options[].label values. Do not invent catalog values.

Custom values: Use the documented values · Include limit: 300 · Exclude limit: 300

Option discovery: Browse without a query; follow nextCursor while hasMore is true.

CSV mapping: companyNaics. Use these exact CSV header keys to check the corresponding source value; missing values and exclusions follow the documented filter semantics.

Select a returned catalog value to generate an exact search request. No catalog value is assumed.

NAICS lookup request

{
  "searchType": "people",
  "field": "account.naics",
  "limit": 100
}

Matching rules

Same default as the UI: Match ANY selected values. Omit matchAll to inherit this default; use boolean false for ANY or true for ALL where supported.

NAICS rule values fragment

{
  "filterRules": {
    "account.naics": {
      "matchAll": false,
      "exclude": false
    }
  }
}

Merge this filterRules fragment into the search request generated after selecting a catalog value.

Rule schema (reference only)

{
  "matchAll": {
    "type": "boolean",
    "default": false
  },
  "exclude": {
    "type": "boolean",
    "default": false
  },
  "condition": {
    "enum": [
      "any",
      "all"
    ],
    "default": "any"
  }
}

account.name · Company Name · filters · people

Select company names from the current catalog.

Accepted type: Select exact catalog values

Shape: string[] of exact current option IDs or readable labels

Call the filter-options option lookup, then submit exact options[].id or options[].label values. Do not invent catalog values.

Custom values: Use the documented values · Include limit: 300 · Exclude limit: 300

Option discovery: Enter at least 2 characters; blank lookup is not a complete catalog.

CSV mapping: company. Use these exact CSV header keys to check the corresponding source value; missing values and exclusions follow the documented filter semantics.

Select a returned catalog value to generate an exact search request. No catalog value is assumed.

Company Name lookup request

{
  "searchType": "people",
  "field": "account.name",
  "limit": 100
}

Matching rules

Same default as the UI: Match ANY selected values. Omit matchAll to inherit this default; use boolean false for ANY or true for ALL where supported.

Company Name rule values fragment

{
  "filterRules": {
    "account.name": {
      "matchAll": false,
      "exclude": false
    }
  }
}

Merge this filterRules fragment into the search request generated after selecting a catalog value.

Rule schema (reference only)

{
  "matchAll": {
    "type": "boolean",
    "default": false
  },
  "exclude": {
    "type": "boolean",
    "default": false
  },
  "condition": {
    "enum": [
      "any",
      "all"
    ],
    "default": "any"
  }
}

account.organictraffic · Organic Traffic · filters · people

Filter by monthly organic website traffic.

Accepted type: Numeric range

Shape: object with grounded min and/or max values

Send a range only when the prompt or campaign strategy gives a real reason for that constraint.

Units: count

Numeric bounds: whole numbers, minimum 0, inclusive endpoints. Zero is preserved.

Custom values: Allowed · Include limit: 300 · Exclude limit: 300

Option discovery: No option lookup needed.

CSV mapping: companyOrganicTraffic. Use these exact CSV header keys to check the corresponding source value; missing values and exclusions follow the documented filter semantics.

Organic Traffic search request

{
  "searchType": "people",
  "filters": {
    "account.organictraffic": {
      "min": 1,
      "max": 100
    }
  },
  "page": 0,
  "size": 3
}

Exclude this value

Organic Traffic exclusion request

{
  "searchType": "people",
  "excludedFilters": {
    "account.organictraffic": {
      "min": 1,
      "max": 100
    }
  },
  "page": 0,
  "size": 3
}

Matching rules

Same default as the UI: Match ANY selected values. Omit matchAll to inherit this default; use boolean false for ANY or true for ALL where supported.

Organic Traffic search request with rules

{
  "searchType": "people",
  "filters": {
    "account.organictraffic": {
      "min": 1,
      "max": 100
    }
  },
  "page": 0,
  "size": 3,
  "filterRules": {
    "account.organictraffic": {
      "matchAll": false,
      "exclude": false
    }
  }
}

Rule schema (reference only)

{
  "matchAll": {
    "type": "boolean",
    "default": false
  },
  "exclude": {
    "type": "boolean",
    "default": false
  },
  "condition": {
    "enum": [
      "any",
      "all"
    ],
    "default": "any"
  }
}

account.paidtraffic · Paid Traffic · filters · people

Filter by monthly paid website traffic.

Accepted type: Numeric range

Shape: object with grounded min and/or max values

Send a range only when the prompt or campaign strategy gives a real reason for that constraint.

Units: count

Numeric bounds: whole numbers, minimum 0, inclusive endpoints. Zero is preserved.

Custom values: Allowed · Include limit: 300 · Exclude limit: 300

Option discovery: No option lookup needed.

CSV mapping: companyPaidTraffic. Use these exact CSV header keys to check the corresponding source value; missing values and exclusions follow the documented filter semantics.

Paid Traffic search request

{
  "searchType": "people",
  "filters": {
    "account.paidtraffic": {
      "min": 1,
      "max": 100
    }
  },
  "page": 0,
  "size": 3
}

Exclude this value

Paid Traffic exclusion request

{
  "searchType": "people",
  "excludedFilters": {
    "account.paidtraffic": {
      "min": 1,
      "max": 100
    }
  },
  "page": 0,
  "size": 3
}

Matching rules

Same default as the UI: Match ANY selected values. Omit matchAll to inherit this default; use boolean false for ANY or true for ALL where supported.

Paid Traffic search request with rules

{
  "searchType": "people",
  "filters": {
    "account.paidtraffic": {
      "min": 1,
      "max": 100
    }
  },
  "page": 0,
  "size": 3,
  "filterRules": {
    "account.paidtraffic": {
      "matchAll": false,
      "exclude": false
    }
  }
}

Rule schema (reference only)

{
  "matchAll": {
    "type": "boolean",
    "default": false
  },
  "exclude": {
    "type": "boolean",
    "default": false
  },
  "condition": {
    "enum": [
      "any",
      "all"
    ],
    "default": "any"
  }
}

account.revenue · Annual Revenue · filters · people

Filter companies by annual revenue range.

Accepted type: Numeric range

Shape: object with grounded min and/or max values

Send a range only when the prompt or campaign strategy gives a real reason for that constraint.

Units: USD

Custom values: Allowed · Include limit: 300 · Exclude limit: 300

Option discovery: No option lookup needed.

CSV mapping: companyRevenue. Related CSV columns are listed. Matching can span multiple source fields, use fallback values or derived conditions; these columns alone do not prove every predicate.

Annual Revenue search request

{
  "searchType": "people",
  "filters": {
    "account.revenue": {
      "min": 1000000,
      "max": 10000000
    }
  },
  "page": 0,
  "size": 3
}

Exclude this value

Annual Revenue exclusion request

{
  "searchType": "people",
  "excludedFilters": {
    "account.revenue": {
      "min": 1000000,
      "max": 10000000
    }
  },
  "page": 0,
  "size": 3
}

Matching rules

Same default as the UI: Match ANY selected values. Omit matchAll to inherit this default; use boolean false for ANY or true for ALL where supported.

Annual Revenue search request with rules

{
  "searchType": "people",
  "filters": {
    "account.revenue": {
      "min": 1000000,
      "max": 10000000
    }
  },
  "page": 0,
  "size": 3,
  "filterRules": {
    "account.revenue": {
      "matchAll": false,
      "exclude": false
    }
  }
}

Rule schema (reference only)

{
  "matchAll": {
    "type": "boolean",
    "default": false
  },
  "exclude": {
    "type": "boolean",
    "default": false
  },
  "condition": {
    "enum": [
      "any",
      "all"
    ],
    "default": "any"
  }
}

account.sic · SIC Codes · filters · people

Filter by exact SIC values. Keep leading zeros and complete returned values.

Accepted type: Select exact catalog values

Shape: string[] of exact current option IDs or readable labels

Call the filter-options option lookup, then submit exact options[].id or options[].label values. Do not invent catalog values.

Custom values: Use the documented values · Include limit: 300 · Exclude limit: 300

Option discovery: Browse without a query; follow nextCursor while hasMore is true.

CSV mapping: companySicCodes. Use these exact CSV header keys to check the corresponding source value; missing values and exclusions follow the documented filter semantics.

Select a returned catalog value to generate an exact search request. No catalog value is assumed.

SIC Codes lookup request

{
  "searchType": "people",
  "field": "account.sic",
  "limit": 100
}

Matching rules

Same default as the UI: Match ANY selected values. Omit matchAll to inherit this default; use boolean false for ANY or true for ALL where supported.

SIC Codes rule values fragment

{
  "filterRules": {
    "account.sic": {
      "matchAll": false,
      "exclude": false
    }
  }
}

Merge this filterRules fragment into the search request generated after selecting a catalog value.

Rule schema (reference only)

{
  "matchAll": {
    "type": "boolean",
    "default": false
  },
  "exclude": {
    "type": "boolean",
    "default": false
  },
  "condition": {
    "enum": [
      "any",
      "all"
    ],
    "default": "any"
  }
}

account.technology · Technologies · filters · people

Filter companies by technologies detected on their sites or stacks.

Accepted type: Select exact catalog values

Shape: string[] of exact current option IDs or readable labels

Call the filter-options option lookup, then submit exact options[].id or options[].label values. Do not invent catalog values.

Custom values: Use the documented values · Include limit: 300 · Exclude limit: 300

Option discovery: Browse without a query; follow nextCursor while hasMore is true.

CSV mapping: companyTechnologies. Related CSV columns are listed. Matching can span multiple source fields, use fallback values or derived conditions; these columns alone do not prove every predicate.

Select a returned catalog value to generate an exact search request. No catalog value is assumed.

Technologies lookup request

{
  "searchType": "people",
  "field": "account.technology",
  "limit": 100
}

Matching rules

Same default as the UI: Match ANY selected values. Omit matchAll to inherit this default; use boolean false for ANY or true for ALL where supported.

Technologies rule values fragment

{
  "filterRules": {
    "account.technology": {
      "matchAll": false,
      "exclude": false,
      "mode": "SMART"
    }
  }
}

Merge this filterRules fragment into the search request generated after selecting a catalog value.

Rule schema (reference only)

{
  "matchAll": {
    "type": "boolean",
    "default": false
  },
  "exclude": {
    "type": "boolean",
    "default": false
  },
  "mode": {
    "enum": [
      "SMART",
      "WORD",
      "STRICT"
    ],
    "default": "SMART"
  },
  "condition": {
    "enum": [
      "any",
      "all"
    ],
    "default": "any"
  }
}

account.traffic · Website Traffic · filters · people

Filter by company website traffic count.

Accepted type: Numeric range

Shape: object with grounded min and/or max values

Send a range only when the prompt or campaign strategy gives a real reason for that constraint.

Units: count

Custom values: Allowed · Include limit: 300 · Exclude limit: 300

Option discovery: No option lookup needed.

CSV mapping: companyTraffic. Use these exact CSV header keys to check the corresponding source value; missing values and exclusions follow the documented filter semantics.

Website Traffic search request

{
  "searchType": "people",
  "filters": {
    "account.traffic": {
      "min": 1,
      "max": 100
    }
  },
  "page": 0,
  "size": 3
}

Exclude this value

Website Traffic exclusion request

{
  "searchType": "people",
  "excludedFilters": {
    "account.traffic": {
      "min": 1,
      "max": 100
    }
  },
  "page": 0,
  "size": 3
}

Matching rules

Same default as the UI: Match ANY selected values. Omit matchAll to inherit this default; use boolean false for ANY or true for ALL where supported.

Website Traffic search request with rules

{
  "searchType": "people",
  "filters": {
    "account.traffic": {
      "min": 1,
      "max": 100
    }
  },
  "page": 0,
  "size": 3,
  "filterRules": {
    "account.traffic": {
      "matchAll": false,
      "exclude": false
    }
  }
}

Rule schema (reference only)

{
  "matchAll": {
    "type": "boolean",
    "default": false
  },
  "exclude": {
    "type": "boolean",
    "default": false
  },
  "condition": {
    "enum": [
      "any",
      "all"
    ],
    "default": "any"
  }
}

account.type · Company Type · filters · people

Filter companies by type, such as private, public, nonprofit, or government.

Accepted type: Select exact catalog values

Shape: string[] of exact current option IDs or readable labels

Call the filter-options option lookup, then submit exact options[].id or options[].label values. Do not invent catalog values.

Custom values: Use the documented values · Include limit: 300 · Exclude limit: 300

Option discovery: Browse without a query; follow nextCursor while hasMore is true.

CSV mapping: companyType. Use these exact CSV header keys to check the corresponding source value; missing values and exclusions follow the documented filter semantics.

Select a returned catalog value to generate an exact search request. No catalog value is assumed.

Company Type lookup request

{
  "searchType": "people",
  "field": "account.type",
  "limit": 100
}

Matching rules

Same default as the UI: Match ANY selected values. Omit matchAll to inherit this default; use boolean false for ANY or true for ALL where supported.

Company Type rule values fragment

{
  "filterRules": {
    "account.type": {
      "matchAll": false,
      "exclude": false
    }
  }
}

Merge this filterRules fragment into the search request generated after selecting a catalog value.

Rule schema (reference only)

{
  "matchAll": {
    "type": "boolean",
    "default": false
  },
  "exclude": {
    "type": "boolean",
    "default": false
  },
  "condition": {
    "enum": [
      "any",
      "all"
    ],
    "default": "any"
  }
}

account.website · Company Website · textFilters · people

Filter by an exact company website URL.

Accepted type: Exact domain or URL

Shape: string or string[] of exact domains or URLs

Send an exact domain, LinkedIn URL, or website URL. A valid request can return zero matches when the value is not in the dataset.

Custom values: Allowed · Include limit: 300 · Exclude limit: 300

Option discovery: No option lookup needed.

CSV mapping: companyWebsite. Use these exact CSV header keys to check the corresponding source value; missing values and exclusions follow the documented filter semantics.

Company Website search request

{
  "searchType": "people",
  "textFilters": {
    "account.website": "https://example.com"
  },
  "page": 0,
  "size": 3
}

Exclude this value

Company Website exclusion request

{
  "searchType": "people",
  "excludedFilters": {
    "account.website": "https://example.com"
  },
  "page": 0,
  "size": 3
}

Matching rules

Same default as the UI: Match ANY selected values. Omit matchAll to inherit this default; use boolean false for ANY or true for ALL where supported.

Company Website search request with rules

{
  "searchType": "people",
  "textFilters": {
    "account.website": "https://example.com"
  },
  "page": 0,
  "size": 3,
  "filterRules": {
    "account.website": {
      "matchAll": false,
      "exclude": false
    }
  }
}

Rule schema (reference only)

{
  "matchAll": {
    "type": "boolean",
    "default": false
  },
  "exclude": {
    "type": "boolean",
    "default": false
  },
  "condition": {
    "enum": [
      "any",
      "all"
    ],
    "default": "any"
  }
}

account.websiteforsale · Website for Sale · filters · people

Filter by the company website-for-sale flag.

Accepted type: Yes / No (true / false)

Shape: boolean, "true"/"false", or an array containing one of those values

Send true or false (or the string "true"/"false"). No catalog lookup is needed.

No matches explicitly stored false values. Unknown values are separate; exclude true to also include unknown values.

Custom values: Use the documented values · Include limit: 300 · Exclude limit: 300

Option discovery: No option lookup needed.

CSV mapping: companyWebsiteForSale. Use these exact CSV header keys to check the corresponding source value; missing values and exclusions follow the documented filter semantics.

Website for Sale search request

{
  "searchType": "people",
  "filters": {
    "account.websiteforsale": [
      "true"
    ]
  },
  "page": 0,
  "size": 3
}

Exclude this value

Website for Sale exclusion request

{
  "searchType": "people",
  "excludedFilters": {
    "account.websiteforsale": [
      "true"
    ]
  },
  "page": 0,
  "size": 3
}

Matching rules

Same default as the UI: Match ANY selected values. Omit matchAll to inherit this default; use boolean false for ANY or true for ALL where supported.

Website for Sale search request with rules

{
  "searchType": "people",
  "filters": {
    "account.websiteforsale": [
      "true"
    ]
  },
  "page": 0,
  "size": 3,
  "filterRules": {
    "account.websiteforsale": {
      "matchAll": false,
      "exclude": false
    }
  }
}

Rule schema (reference only)

{
  "matchAll": {
    "type": "boolean",
    "default": false
  },
  "exclude": {
    "type": "boolean",
    "default": false
  },
  "condition": {
    "enum": [
      "any",
      "all"
    ],
    "default": "any"
  }
}

contact.certification · Certifications · filters · people

Filter by certifications.

Accepted type: Select exact catalog values

Shape: string[] of exact current option IDs or readable labels

Call the filter-options option lookup, then submit exact options[].id or options[].label values. Do not invent catalog values.

Custom values: Use the documented values · Include limit: 300 · Exclude limit: 300

Option discovery: Enter at least 2 characters; blank lookup is not a complete catalog.

CSV mapping: certifications. Use these exact CSV header keys to check the corresponding source value; missing values and exclusions follow the documented filter semantics.

Select a returned catalog value to generate an exact search request. No catalog value is assumed.

Certifications lookup request

{
  "searchType": "people",
  "field": "contact.certification",
  "limit": 100
}

Matching rules

Same default as the UI: Match ANY selected values. Omit matchAll to inherit this default; use boolean false for ANY or true for ALL where supported.

Certifications rule values fragment

{
  "filterRules": {
    "contact.certification": {
      "matchAll": false,
      "exclude": false
    }
  }
}

Merge this filterRules fragment into the search request generated after selecting a catalog value.

Rule schema (reference only)

{
  "matchAll": {
    "type": "boolean",
    "default": false
  },
  "exclude": {
    "type": "boolean",
    "default": false
  },
  "condition": {
    "enum": [
      "any",
      "all"
    ],
    "default": "any"
  }
}

contact.company.current · Current Company · filters · people

Filter contacts by current company name.

Accepted type: Select exact catalog values

Shape: string[] of exact current option IDs or readable labels

Call the filter-options option lookup, then submit exact options[].id or options[].label values. Do not invent catalog values.

Custom values: Use the documented values · Include limit: 300 · Exclude limit: 300

Option discovery: Enter at least 2 characters; blank lookup is not a complete catalog.

CSV mapping: company, companyDomain, companyWebsite, companyLinkedin. Related CSV columns are listed. Matching can span multiple source fields, use fallback values or derived conditions; these columns alone do not prove every predicate.

Select a returned catalog value to generate an exact search request. No catalog value is assumed.

Current Company lookup request

{
  "searchType": "people",
  "field": "contact.company.current",
  "limit": 100
}

Matching rules

Same default as the UI: Match ANY selected values. Omit matchAll to inherit this default; use boolean false for ANY or true for ALL where supported.

Current Company rule values fragment

{
  "filterRules": {
    "contact.company.current": {
      "matchAll": false,
      "exclude": false,
      "mode": "SMART"
    }
  }
}

Merge this filterRules fragment into the search request generated after selecting a catalog value.

Rule schema (reference only)

{
  "matchAll": {
    "type": "boolean",
    "default": false
  },
  "exclude": {
    "type": "boolean",
    "default": false
  },
  "mode": {
    "enum": [
      "SMART",
      "WORD",
      "STRICT"
    ],
    "default": "SMART"
  },
  "condition": {
    "enum": [
      "any",
      "all"
    ],
    "default": "any"
  }
}

contact.departmentandfunction · Department · filters · people

Filter contacts by department or job function.

Accepted type: Select exact catalog values

Shape: string[] of exact current option IDs or readable labels

Call the filter-options option lookup, then submit exact options[].id or options[].label values. Do not invent catalog values.

Custom values: Use the documented values · Include limit: 300 · Exclude limit: 300

Option discovery: Browse without a query; follow nextCursor while hasMore is true.

CSV mapping: department. Use these exact CSV header keys to check the corresponding source value; missing values and exclusions follow the documented filter semantics.

Select a returned catalog value to generate an exact search request. No catalog value is assumed.

Department lookup request

{
  "searchType": "people",
  "field": "contact.departmentandfunction",
  "limit": 100
}

Matching rules

Same default as the UI: Match ANY selected values. Omit matchAll to inherit this default; use boolean false for ANY or true for ALL where supported.

Department rule values fragment

{
  "filterRules": {
    "contact.departmentandfunction": {
      "matchAll": false,
      "exclude": false
    }
  }
}

Merge this filterRules fragment into the search request generated after selecting a catalog value.

Rule schema (reference only)

{
  "matchAll": {
    "type": "boolean",
    "default": false
  },
  "exclude": {
    "type": "boolean",
    "default": false
  },
  "condition": {
    "enum": [
      "any",
      "all"
    ],
    "default": "any"
  }
}

contact.education.date · Education Date · filters · people

Filter by education year range.

Accepted type: Numeric range

Shape: object with grounded min and/or max values

Send a range only when the prompt or campaign strategy gives a real reason for that constraint.

Units: year

Custom values: Allowed · Include limit: 300 · Exclude limit: 300

Option discovery: No option lookup needed.

CSV mapping: educationCompletionYear. Use these exact CSV header keys to check the corresponding source value; missing values and exclusions follow the documented filter semantics.

Education Date search request

{
  "searchType": "people",
  "filters": {
    "contact.education.date": {
      "min": 2010,
      "max": 2025
    }
  },
  "page": 0,
  "size": 3
}

Exclude this value

Education Date exclusion request

{
  "searchType": "people",
  "excludedFilters": {
    "contact.education.date": {
      "min": 2010,
      "max": 2025
    }
  },
  "page": 0,
  "size": 3
}

Matching rules

Same default as the UI: Match ANY selected values. Omit matchAll to inherit this default; use boolean false for ANY or true for ALL where supported.

Education Date search request with rules

{
  "searchType": "people",
  "filters": {
    "contact.education.date": {
      "min": 2010,
      "max": 2025
    }
  },
  "page": 0,
  "size": 3,
  "filterRules": {
    "contact.education.date": {
      "matchAll": false,
      "exclude": false
    }
  }
}

Rule schema (reference only)

{
  "matchAll": {
    "type": "boolean",
    "default": false
  },
  "exclude": {
    "type": "boolean",
    "default": false
  },
  "condition": {
    "enum": [
      "any",
      "all"
    ],
    "default": "any"
  }
}

contact.education.degree · Education Degree · filters · people

Filter by education degree.

Accepted type: Select exact catalog values

Shape: string[] of exact current option IDs or readable labels

Call the filter-options option lookup, then submit exact options[].id or options[].label values. Do not invent catalog values.

Custom values: Use the documented values · Include limit: 300 · Exclude limit: 300

Option discovery: Enter at least 2 characters; blank lookup is not a complete catalog.

CSV mapping: educationDegree. Use these exact CSV header keys to check the corresponding source value; missing values and exclusions follow the documented filter semantics.

Select a returned catalog value to generate an exact search request. No catalog value is assumed.

Education Degree lookup request

{
  "searchType": "people",
  "field": "contact.education.degree",
  "limit": 100
}

Matching rules

Same default as the UI: Match ANY selected values. Omit matchAll to inherit this default; use boolean false for ANY or true for ALL where supported.

Education Degree rule values fragment

{
  "filterRules": {
    "contact.education.degree": {
      "matchAll": false,
      "exclude": false
    }
  }
}

Merge this filterRules fragment into the search request generated after selecting a catalog value.

Rule schema (reference only)

{
  "matchAll": {
    "type": "boolean",
    "default": false
  },
  "exclude": {
    "type": "boolean",
    "default": false
  },
  "condition": {
    "enum": [
      "any",
      "all"
    ],
    "default": "any"
  }
}

contact.emailverificationdate · Email Verification Date · filters · people

Filter by the date an email was last verified.

Accepted type: Calendar date range

Shape: object with ISO 8601 min and/or max dates (YYYY-MM-DD)

Send ISO 8601 calendar dates as min and/or max; do not use numeric timestamps.

Units: ISO 8601 date (YYYY-MM-DD)

Custom values: Allowed · Include limit: 300 · Exclude limit: 300

Option discovery: No option lookup needed.

CSV mapping: emailLastVerifiedDate. Use these exact CSV header keys to check the corresponding source value; missing values and exclusions follow the documented filter semantics.

Email Verification Date search request

{
  "searchType": "people",
  "filters": {
    "contact.emailverificationdate": {
      "min": "2024-01-01",
      "max": "2026-01-01"
    }
  },
  "page": 0,
  "size": 3
}

Exclude this value

Email Verification Date exclusion request

{
  "searchType": "people",
  "excludedFilters": {
    "contact.emailverificationdate": {
      "min": "2024-01-01",
      "max": "2026-01-01"
    }
  },
  "page": 0,
  "size": 3
}

Matching rules

Same default as the UI: Match ANY selected values. Omit matchAll to inherit this default; use boolean false for ANY or true for ALL where supported.

Email Verification Date search request with rules

{
  "searchType": "people",
  "filters": {
    "contact.emailverificationdate": {
      "min": "2024-01-01",
      "max": "2026-01-01"
    }
  },
  "page": 0,
  "size": 3,
  "filterRules": {
    "contact.emailverificationdate": {
      "matchAll": false,
      "exclude": false
    }
  }
}

Rule schema (reference only)

{
  "matchAll": {
    "type": "boolean",
    "default": false
  },
  "exclude": {
    "type": "boolean",
    "default": false
  },
  "condition": {
    "enum": [
      "any",
      "all"
    ],
    "default": "any"
  }
}

contact.experience.latest.duration · Experience Duration · filters · people

Filter by time spent in the latest role, in months.

Accepted type: Numeric range

Shape: object with grounded min and/or max values

Send a range only when the prompt or campaign strategy gives a real reason for that constraint.

Units: months

Custom values: Allowed · Include limit: 300 · Exclude limit: 300

Option discovery: No option lookup needed.

CSV mapping: jobStartDate. Use these exact CSV header keys to check the corresponding source value; missing values and exclusions follow the documented filter semantics.

Experience Duration search request

{
  "searchType": "people",
  "filters": {
    "contact.experience.latest.duration": {
      "min": 12,
      "max": 36
    }
  },
  "page": 0,
  "size": 3
}

Exclude this value

Experience Duration exclusion request

{
  "searchType": "people",
  "excludedFilters": {
    "contact.experience.latest.duration": {
      "min": 12,
      "max": 36
    }
  },
  "page": 0,
  "size": 3
}

Matching rules

Same default as the UI: Match ANY selected values. Omit matchAll to inherit this default; use boolean false for ANY or true for ALL where supported.

Experience Duration search request with rules

{
  "searchType": "people",
  "filters": {
    "contact.experience.latest.duration": {
      "min": 12,
      "max": 36
    }
  },
  "page": 0,
  "size": 3,
  "filterRules": {
    "contact.experience.latest.duration": {
      "matchAll": false,
      "exclude": false
    }
  }
}

Rule schema (reference only)

{
  "matchAll": {
    "type": "boolean",
    "default": false
  },
  "exclude": {
    "type": "boolean",
    "default": false
  },
  "condition": {
    "enum": [
      "any",
      "all"
    ],
    "default": "any"
  }
}

contact.experience.latest.title · Job Title · filters · people

Filter by latest or current job title.

Accepted type: Text values

Shape: string[] of current job-title text

Send current job-title text. Suggestions are optional and do not restrict submitted titles.

Custom values: Allowed · Include limit: 300 · Exclude limit: 300

Option discovery: Blank lookup returns a starter sample. Type a query for broader discovery.

CSV mapping: title. Related CSV columns are listed. Matching can span multiple source fields, use fallback values or derived conditions; these columns alone do not prove every predicate.

Job Title search request

{
  "searchType": "people",
  "filters": {
    "contact.experience.latest.title": [
      "QA Engineer"
    ]
  },
  "page": 0,
  "size": 3
}

Exclude this value

Job Title exclusion request

{
  "searchType": "people",
  "excludedFilters": {
    "contact.experience.latest.title": [
      "QA Engineer"
    ]
  },
  "page": 0,
  "size": 3
}

Job Title lookup request

{
  "searchType": "people",
  "field": "contact.experience.latest.title",
  "limit": 100
}

Matching rules

Same default as the UI: Match ANY selected values. Omit matchAll to inherit this default; use boolean false for ANY or true for ALL where supported.

Job Title search request with rules

{
  "searchType": "people",
  "filters": {
    "contact.experience.latest.title": [
      "QA Engineer"
    ]
  },
  "page": 0,
  "size": 3,
  "filterRules": {
    "contact.experience.latest.title": {
      "matchAll": false,
      "exclude": false,
      "mode": "SMART"
    }
  }
}

Rule schema (reference only)

{
  "matchAll": {
    "type": "boolean",
    "default": false
  },
  "exclude": {
    "type": "boolean",
    "default": false
  },
  "mode": {
    "enum": [
      "SMART",
      "WORD",
      "STRICT"
    ],
    "default": "SMART"
  },
  "condition": {
    "enum": [
      "any",
      "all"
    ],
    "default": "any"
  }
}

contact.fullname · Contact Name · textFilters · people

Find names using all-word matching, not strict exact-name matching.

Accepted type: Text values

Shape: string or string[] of concise values

Custom values are allowed, but keep them short and directly tied to what this filter matches.

Custom values: Allowed · Include limit: 300 · Exclude limit: 300

Option discovery: No option lookup needed.

CSV mapping: name. Related CSV columns are listed. Matching can span multiple source fields, use fallback values or derived conditions; these columns alone do not prove every predicate.

Contact Name search request

{
  "searchType": "people",
  "textFilters": {
    "contact.fullname": "Sarah Chen"
  },
  "page": 0,
  "size": 3
}

Exclude this value

Contact Name exclusion request

{
  "searchType": "people",
  "excludedFilters": {
    "contact.fullname": "Sarah Chen"
  },
  "page": 0,
  "size": 3
}

Matching rules

Same default as the UI: Match ANY selected values. Omit matchAll to inherit this default; use boolean false for ANY or true for ALL where supported.

Contact Name search request with rules

{
  "searchType": "people",
  "textFilters": {
    "contact.fullname": "Sarah Chen"
  },
  "page": 0,
  "size": 3,
  "filterRules": {
    "contact.fullname": {
      "matchAll": false,
      "exclude": false,
      "mode": "SMART"
    }
  }
}

Rule schema (reference only)

{
  "matchAll": {
    "type": "boolean",
    "default": false
  },
  "exclude": {
    "type": "boolean",
    "default": false
  },
  "mode": {
    "enum": [
      "SMART",
      "WORD",
      "STRICT"
    ],
    "default": "SMART"
  },
  "condition": {
    "enum": [
      "any",
      "all"
    ],
    "default": "any"
  }
}

contact.hascellphone · Mobile Available · filters · people

Filter by personal mobile availability.

Accepted type: Yes / No (true / false)

Shape: boolean, "true"/"false", or an array containing one of those values

Send true or false (or the string "true"/"false"). No catalog lookup is needed.

Custom values: Use the documented values · Include limit: 300 · Exclude limit: 300

Option discovery: No option lookup needed.

CSV mapping: personalMobileAvailable. Use these exact CSV header keys to check the corresponding source value; missing values and exclusions follow the documented filter semantics.

Mobile Available search request

{
  "searchType": "people",
  "filters": {
    "contact.hascellphone": [
      "true"
    ]
  },
  "page": 0,
  "size": 3
}

Exclude this value

Mobile Available exclusion request

{
  "searchType": "people",
  "excludedFilters": {
    "contact.hascellphone": [
      "true"
    ]
  },
  "page": 0,
  "size": 3
}

Matching rules

Same default as the UI: Match ANY selected values. Omit matchAll to inherit this default; use boolean false for ANY or true for ALL where supported.

Mobile Available search request with rules

{
  "searchType": "people",
  "filters": {
    "contact.hascellphone": [
      "true"
    ]
  },
  "page": 0,
  "size": 3,
  "filterRules": {
    "contact.hascellphone": {
      "matchAll": false,
      "exclude": false
    }
  }
}

Rule schema (reference only)

{
  "matchAll": {
    "type": "boolean",
    "default": false
  },
  "exclude": {
    "type": "boolean",
    "default": false
  },
  "condition": {
    "enum": [
      "any",
      "all"
    ],
    "default": "any"
  }
}

contact.hasemail · Work Email Available · filters · people

Filter by work email availability.

Accepted type: Yes / No (true / false)

Shape: boolean, "true"/"false", or an array containing one of those values

Send true or false (or the string "true"/"false"). No catalog lookup is needed.

Custom values: Use the documented values · Include limit: 300 · Exclude limit: 300

Option discovery: No option lookup needed.

CSV mapping: workEmailAvailable. Use these exact CSV header keys to check the corresponding source value; missing values and exclusions follow the documented filter semantics.

Work Email Available search request

{
  "searchType": "people",
  "filters": {
    "contact.hasemail": [
      "true"
    ]
  },
  "page": 0,
  "size": 3
}

Exclude this value

Work Email Available exclusion request

{
  "searchType": "people",
  "excludedFilters": {
    "contact.hasemail": [
      "true"
    ]
  },
  "page": 0,
  "size": 3
}

Matching rules

Same default as the UI: Match ANY selected values. Omit matchAll to inherit this default; use boolean false for ANY or true for ALL where supported.

Work Email Available search request with rules

{
  "searchType": "people",
  "filters": {
    "contact.hasemail": [
      "true"
    ]
  },
  "page": 0,
  "size": 3,
  "filterRules": {
    "contact.hasemail": {
      "matchAll": false,
      "exclude": false
    }
  }
}

Rule schema (reference only)

{
  "matchAll": {
    "type": "boolean",
    "default": false
  },
  "exclude": {
    "type": "boolean",
    "default": false
  },
  "condition": {
    "enum": [
      "any",
      "all"
    ],
    "default": "any"
  }
}

contact.joblocation · Job Location · filters · people

Filter by current job location, separately from the person's location or employer headquarters.

Accepted type: Select exact catalog values

Shape: string[] of exact current option IDs or readable labels

Call the filter-options option lookup, then submit exact options[].id or options[].label values. Do not invent catalog values.

Custom values: Use the documented values · Include limit: 300 · Exclude limit: 300

Option discovery: Enter at least 2 characters; blank lookup is not a complete catalog.

CSV mapping: jobLocation. Related CSV columns are listed. Matching can span multiple source fields, use fallback values or derived conditions; these columns alone do not prove every predicate.

Job Location search request

{
  "searchType": "people",
  "filters": {
    "contact.joblocation": [
      "United States"
    ]
  },
  "page": 0,
  "size": 3
}

Exclude this value

Job Location exclusion request

{
  "searchType": "people",
  "excludedFilters": {
    "contact.joblocation": [
      "United States"
    ]
  },
  "page": 0,
  "size": 3
}

Job Location lookup request

{
  "searchType": "people",
  "field": "contact.joblocation",
  "limit": 100
}

Matching rules

Same default as the UI: Match ANY selected values. Omit matchAll to inherit this default; use boolean false for ANY or true for ALL where supported.

Job Location search request with rules

{
  "searchType": "people",
  "filters": {
    "contact.joblocation": [
      "United States"
    ]
  },
  "page": 0,
  "size": 3,
  "filterRules": {
    "contact.joblocation": {
      "matchAll": false,
      "exclude": false
    }
  }
}

Rule schema (reference only)

{
  "matchAll": {
    "type": "boolean",
    "default": false
  },
  "exclude": {
    "type": "boolean",
    "default": false
  },
  "condition": {
    "enum": [
      "any",
      "all"
    ],
    "default": "any"
  }
}

contact.keyword · Keywords · textFilters · people

Search supported person sources for keywords.

Accepted type: Text values

Shape: string or string[] of short keyword terms

Custom values are allowed, but keep them concise buyer-side terms. Do not send full prompts or sentences.

Custom values: Allowed · Include limit: 300 · Exclude limit: 300

Option discovery: No option lookup needed.

CSV mapping: headline, title, skills, certifications. Related CSV columns are listed. Matching can span multiple source fields, use fallback values or derived conditions; these columns alone do not prove every predicate.

Keywords search request

{
  "searchType": "people",
  "textFilters": {
    "contact.keyword": "outbound sales"
  },
  "page": 0,
  "size": 3
}

Exclude this value

Keywords exclusion request

{
  "searchType": "people",
  "excludedFilters": {
    "contact.keyword": "outbound sales"
  },
  "page": 0,
  "size": 3
}

Matching rules

Same default as the UI: Match ANY selected values. Omit matchAll to inherit this default; use boolean false for ANY or true for ALL where supported.

Keywords search request with rules

{
  "searchType": "people",
  "textFilters": {
    "contact.keyword": "outbound sales"
  },
  "page": 0,
  "size": 3,
  "filterRules": {
    "contact.keyword": {
      "matchAll": false,
      "exclude": false,
      "mode": "SMART"
    }
  }
}

Rule schema (reference only)

{
  "matchAll": {
    "type": "boolean",
    "default": false
  },
  "exclude": {
    "type": "boolean",
    "default": false
  },
  "mode": {
    "enum": [
      "SMART",
      "WORD",
      "STRICT"
    ],
    "default": "SMART"
  },
  "condition": {
    "enum": [
      "any",
      "all"
    ],
    "default": "any"
  },
  "sources": {
    "type": "array",
    "items": {
      "enum": [
        "TITLE",
        "JOB_DESCRIPTION",
        "HEADLINE",
        "ABOUT",
        "SKILLS",
        "CERTIFICATIONS",
        "LANGUAGES"
      ]
    }
  },
  "includeSources": {
    "type": "array",
    "items": {
      "enum": [
        "TITLE",
        "JOB_DESCRIPTION",
        "HEADLINE",
        "ABOUT",
        "SKILLS",
        "CERTIFICATIONS",
        "LANGUAGES"
      ]
    }
  },
  "excludeSources": {
    "type": "array",
    "items": {
      "enum": [
        "TITLE",
        "JOB_DESCRIPTION",
        "HEADLINE",
        "ABOUT",
        "SKILLS",
        "CERTIFICATIONS",
        "LANGUAGES"
      ]
    }
  }
}

contact.linkedin · LinkedIn URL · textFilters · people

Filter by LinkedIn profile URL.

Accepted type: Exact domain or URL

Shape: string or string[] of exact domains or URLs

Send an exact domain, LinkedIn URL, or website URL. A valid request can return zero matches when the value is not in the dataset.

Custom values: Allowed · Include limit: 10000 · Exclude limit: 10000

Option discovery: No option lookup needed.

CSV mapping: linkedin. Use these exact CSV header keys to check the corresponding source value; missing values and exclusions follow the documented filter semantics.

LinkedIn URL search request

{
  "searchType": "people",
  "textFilters": {
    "contact.linkedin": "https://www.linkedin.com/in/example"
  },
  "page": 0,
  "size": 3
}

Exclude this value

LinkedIn URL exclusion request

{
  "searchType": "people",
  "excludedFilters": {
    "contact.linkedin": "https://www.linkedin.com/in/example"
  },
  "page": 0,
  "size": 3
}

Matching rules

Same default as the UI: Match ANY selected values. Omit matchAll to inherit this default; use boolean false for ANY or true for ALL where supported.

LinkedIn URL search request with rules

{
  "searchType": "people",
  "textFilters": {
    "contact.linkedin": "https://www.linkedin.com/in/example"
  },
  "page": 0,
  "size": 3,
  "filterRules": {
    "contact.linkedin": {
      "matchAll": false,
      "exclude": false
    }
  }
}

Rule schema (reference only)

{
  "matchAll": {
    "type": "boolean",
    "default": false
  },
  "exclude": {
    "type": "boolean",
    "default": false
  },
  "condition": {
    "enum": [
      "any",
      "all"
    ],
    "default": "any"
  }
}

contact.linkedinconnections · LinkedIn Connections · filters · people

Filter by the person's LinkedIn connection count.

Accepted type: Numeric range

Shape: object with grounded min and/or max values

Send a range only when the prompt or campaign strategy gives a real reason for that constraint.

Units: count

Custom values: Allowed · Include limit: 300 · Exclude limit: 300

Option discovery: No option lookup needed.

CSV mapping: linkedinConnections. Use these exact CSV header keys to check the corresponding source value; missing values and exclusions follow the documented filter semantics.

LinkedIn Connections search request

{
  "searchType": "people",
  "filters": {
    "contact.linkedinconnections": {
      "min": 1,
      "max": 100
    }
  },
  "page": 0,
  "size": 3
}

Exclude this value

LinkedIn Connections exclusion request

{
  "searchType": "people",
  "excludedFilters": {
    "contact.linkedinconnections": {
      "min": 1,
      "max": 100
    }
  },
  "page": 0,
  "size": 3
}

Matching rules

Same default as the UI: Match ANY selected values. Omit matchAll to inherit this default; use boolean false for ANY or true for ALL where supported.

LinkedIn Connections search request with rules

{
  "searchType": "people",
  "filters": {
    "contact.linkedinconnections": {
      "min": 1,
      "max": 100
    }
  },
  "page": 0,
  "size": 3,
  "filterRules": {
    "contact.linkedinconnections": {
      "matchAll": false,
      "exclude": false
    }
  }
}

Rule schema (reference only)

{
  "matchAll": {
    "type": "boolean",
    "default": false
  },
  "exclude": {
    "type": "boolean",
    "default": false
  },
  "condition": {
    "enum": [
      "any",
      "all"
    ],
    "default": "any"
  }
}

contact.location · Person Location · filters · people

Person Location filter. Use the value shape and current contract below.

Accepted type: Select exact catalog values

Shape: string[] of exact current option IDs or readable labels

Call the filter-options option lookup, then submit exact options[].id or options[].label values. Do not invent catalog values.

Custom values: Use the documented values · Include limit: 300 · Exclude limit: 300

Option discovery: Enter at least 2 characters; blank lookup is not a complete catalog.

CSV mapping: location, city, state, country. Related CSV columns are listed. Matching can span multiple source fields, use fallback values or derived conditions; these columns alone do not prove every predicate.

Person Location search request

{
  "searchType": "people",
  "filters": {
    "contact.location": [
      "United States"
    ]
  },
  "page": 0,
  "size": 3
}

Exclude this value

Person Location exclusion request

{
  "searchType": "people",
  "excludedFilters": {
    "contact.location": [
      "United States"
    ]
  },
  "page": 0,
  "size": 3
}

Person Location lookup request

{
  "searchType": "people",
  "field": "contact.location",
  "limit": 100
}

Matching rules

Same default as the UI: Match ANY selected values. Omit matchAll to inherit this default; use boolean false for ANY or true for ALL where supported.

Person Location search request with rules

{
  "searchType": "people",
  "filters": {
    "contact.location": [
      "United States"
    ]
  },
  "page": 0,
  "size": 3,
  "filterRules": {
    "contact.location": {
      "matchAll": false,
      "exclude": false
    }
  }
}

Rule schema (reference only)

{
  "matchAll": {
    "type": "boolean",
    "default": false
  },
  "exclude": {
    "type": "boolean",
    "default": false
  },
  "condition": {
    "enum": [
      "any",
      "all"
    ],
    "default": "any"
  }
}

contact.patent · Patents · textFilters · people

Search patent text for the supplied words.

Accepted type: Text values

Shape: string or string[] of concise values

Custom values are allowed, but keep them short and directly tied to what this filter matches.

Custom values: Allowed · Include limit: 300 · Exclude limit: 300

Option discovery: No option lookup needed.

CSV mapping: patents. Related CSV columns are listed. Matching can span multiple source fields, use fallback values or derived conditions; these columns alone do not prove every predicate.

Patents search request

{
  "searchType": "people",
  "textFilters": {
    "contact.patent": "battery"
  },
  "page": 0,
  "size": 3
}

Exclude this value

Patents exclusion request

{
  "searchType": "people",
  "excludedFilters": {
    "contact.patent": "battery"
  },
  "page": 0,
  "size": 3
}

Matching rules

Same default as the UI: Match ANY selected values. Omit matchAll to inherit this default; use boolean false for ANY or true for ALL where supported.

Patents search request with rules

{
  "searchType": "people",
  "textFilters": {
    "contact.patent": "battery"
  },
  "page": 0,
  "size": 3,
  "filterRules": {
    "contact.patent": {
      "matchAll": false,
      "exclude": false,
      "mode": "SMART"
    }
  }
}

Rule schema (reference only)

{
  "matchAll": {
    "type": "boolean",
    "default": false
  },
  "exclude": {
    "type": "boolean",
    "default": false
  },
  "mode": {
    "enum": [
      "SMART",
      "WORD",
      "STRICT"
    ],
    "default": "SMART"
  },
  "condition": {
    "enum": [
      "any",
      "all"
    ],
    "default": "any"
  }
}

contact.persona · Persona · filters · people

Filter by the person's assigned persona from the current catalog.

Accepted type: Select exact catalog values

Shape: string[] of exact current option IDs or readable labels

Call the filter-options option lookup, then submit exact options[].id or options[].label values. Do not invent catalog values.

Custom values: Use the documented values · Include limit: 300 · Exclude limit: 300

Option discovery: Browse without a query; follow nextCursor while hasMore is true.

CSV mapping: persona. Use these exact CSV header keys to check the corresponding source value; missing values and exclusions follow the documented filter semantics.

Select a returned catalog value to generate an exact search request. No catalog value is assumed.

Persona lookup request

{
  "searchType": "people",
  "field": "contact.persona",
  "limit": 100
}

Matching rules

Same default as the UI: Match ANY selected values. Omit matchAll to inherit this default; use boolean false for ANY or true for ALL where supported.

Persona rule values fragment

{
  "filterRules": {
    "contact.persona": {
      "matchAll": false,
      "exclude": false
    }
  }
}

Merge this filterRules fragment into the search request generated after selecting a catalog value.

Rule schema (reference only)

{
  "matchAll": {
    "type": "boolean",
    "default": false
  },
  "exclude": {
    "type": "boolean",
    "default": false
  },
  "condition": {
    "enum": [
      "any",
      "all"
    ],
    "default": "any"
  }
}

contact.personalWebsite · Personal Website · textFilters · people

Filter by an exact personal website URL.

Accepted type: Exact domain or URL

Shape: string or string[] of exact domains or URLs

Send an exact domain, LinkedIn URL, or website URL. A valid request can return zero matches when the value is not in the dataset.

Custom values: Allowed · Include limit: 300 · Exclude limit: 300

Option discovery: No option lookup needed.

CSV mapping: personalWebsite. Use these exact CSV header keys to check the corresponding source value; missing values and exclusions follow the documented filter semantics.

Personal Website search request

{
  "searchType": "people",
  "textFilters": {
    "contact.personalWebsite": "https://example.com"
  },
  "page": 0,
  "size": 3
}

Exclude this value

Personal Website exclusion request

{
  "searchType": "people",
  "excludedFilters": {
    "contact.personalWebsite": "https://example.com"
  },
  "page": 0,
  "size": 3
}

Matching rules

Same default as the UI: Match ANY selected values. Omit matchAll to inherit this default; use boolean false for ANY or true for ALL where supported.

Personal Website search request with rules

{
  "searchType": "people",
  "textFilters": {
    "contact.personalWebsite": "https://example.com"
  },
  "page": 0,
  "size": 3,
  "filterRules": {
    "contact.personalWebsite": {
      "matchAll": false,
      "exclude": false
    }
  }
}

Rule schema (reference only)

{
  "matchAll": {
    "type": "boolean",
    "default": false
  },
  "exclude": {
    "type": "boolean",
    "default": false
  },
  "condition": {
    "enum": [
      "any",
      "all"
    ],
    "default": "any"
  }
}

contact.publication · Publications · textFilters · people

Search publication text for the supplied words.

Accepted type: Text values

Shape: string or string[] of concise values

Custom values are allowed, but keep them short and directly tied to what this filter matches.

Custom values: Allowed · Include limit: 300 · Exclude limit: 300

Option discovery: No option lookup needed.

CSV mapping: publications. Related CSV columns are listed. Matching can span multiple source fields, use fallback values or derived conditions; these columns alone do not prove every predicate.

Publications search request

{
  "searchType": "people",
  "textFilters": {
    "contact.publication": "robotics"
  },
  "page": 0,
  "size": 3
}

Exclude this value

Publications exclusion request

{
  "searchType": "people",
  "excludedFilters": {
    "contact.publication": "robotics"
  },
  "page": 0,
  "size": 3
}

Matching rules

Same default as the UI: Match ANY selected values. Omit matchAll to inherit this default; use boolean false for ANY or true for ALL where supported.

Publications search request with rules

{
  "searchType": "people",
  "textFilters": {
    "contact.publication": "robotics"
  },
  "page": 0,
  "size": 3,
  "filterRules": {
    "contact.publication": {
      "matchAll": false,
      "exclude": false,
      "mode": "SMART"
    }
  }
}

Rule schema (reference only)

{
  "matchAll": {
    "type": "boolean",
    "default": false
  },
  "exclude": {
    "type": "boolean",
    "default": false
  },
  "mode": {
    "enum": [
      "SMART",
      "WORD",
      "STRICT"
    ],
    "default": "SMART"
  },
  "condition": {
    "enum": [
      "any",
      "all"
    ],
    "default": "any"
  }
}

contact.reachable · Any Contact Method Available · filters · people

Filter by whether any supported contact method is available.

Accepted type: Yes / No (true / false)

Shape: boolean, "true"/"false", or an array containing one of those values

Send true or false (or the string "true"/"false"). No catalog lookup is needed.

Custom values: Use the documented values · Include limit: 300 · Exclude limit: 300

Option discovery: No option lookup needed.

CSV mapping: contactMethodAvailable. Use these exact CSV header keys to check the corresponding source value; missing values and exclusions follow the documented filter semantics.

Any Contact Method Available search request

{
  "searchType": "people",
  "filters": {
    "contact.reachable": [
      "true"
    ]
  },
  "page": 0,
  "size": 3
}

Exclude this value

Any Contact Method Available exclusion request

{
  "searchType": "people",
  "excludedFilters": {
    "contact.reachable": [
      "true"
    ]
  },
  "page": 0,
  "size": 3
}

Matching rules

Same default as the UI: Match ANY selected values. Omit matchAll to inherit this default; use boolean false for ANY or true for ALL where supported.

Any Contact Method Available search request with rules

{
  "searchType": "people",
  "filters": {
    "contact.reachable": [
      "true"
    ]
  },
  "page": 0,
  "size": 3,
  "filterRules": {
    "contact.reachable": {
      "matchAll": false,
      "exclude": false
    }
  }
}

Rule schema (reference only)

{
  "matchAll": {
    "type": "boolean",
    "default": false
  },
  "exclude": {
    "type": "boolean",
    "default": false
  },
  "condition": {
    "enum": [
      "any",
      "all"
    ],
    "default": "any"
  }
}

contact.seniority · Seniority · filters · people

Filter contacts by seniority.

Accepted type: Select exact catalog values

Shape: string[] of exact current option IDs or readable labels

Call the filter-options option lookup, then submit exact options[].id or options[].label values. Do not invent catalog values.

Custom values: Use the documented values · Include limit: 300 · Exclude limit: 300

Option discovery: Browse without a query; follow nextCursor while hasMore is true.

CSV mapping: seniority. Use these exact CSV header keys to check the corresponding source value; missing values and exclusions follow the documented filter semantics.

Select a returned catalog value to generate an exact search request. No catalog value is assumed.

Seniority lookup request

{
  "searchType": "people",
  "field": "contact.seniority",
  "limit": 100
}

Matching rules

Same default as the UI: Match ANY selected values. Omit matchAll to inherit this default; use boolean false for ANY or true for ALL where supported.

Seniority rule values fragment

{
  "filterRules": {
    "contact.seniority": {
      "matchAll": false,
      "exclude": false
    }
  }
}

Merge this filterRules fragment into the search request generated after selecting a catalog value.

Rule schema (reference only)

{
  "matchAll": {
    "type": "boolean",
    "default": false
  },
  "exclude": {
    "type": "boolean",
    "default": false
  },
  "condition": {
    "enum": [
      "any",
      "all"
    ],
    "default": "any"
  }
}

contact.skill · Skills · filters · people

Filter by skills.

Accepted type: Select exact catalog values

Shape: string[] of exact current option IDs or readable labels

Call the filter-options option lookup, then submit exact options[].id or options[].label values. Do not invent catalog values.

Custom values: Use the documented values · Include limit: 300 · Exclude limit: 300

Option discovery: Enter at least 2 characters; blank lookup is not a complete catalog.

CSV mapping: skills. Related CSV columns are listed. Matching can span multiple source fields, use fallback values or derived conditions; these columns alone do not prove every predicate.

Select a returned catalog value to generate an exact search request. No catalog value is assumed.

Skills lookup request

{
  "searchType": "people",
  "field": "contact.skill",
  "limit": 100
}

Matching rules

Same default as the UI: Match ANY selected values. Omit matchAll to inherit this default; use boolean false for ANY or true for ALL where supported.

Skills rule values fragment

{
  "filterRules": {
    "contact.skill": {
      "matchAll": false,
      "exclude": false,
      "mode": "SMART"
    }
  }
}

Merge this filterRules fragment into the search request generated after selecting a catalog value.

Rule schema (reference only)

{
  "matchAll": {
    "type": "boolean",
    "default": false
  },
  "exclude": {
    "type": "boolean",
    "default": false
  },
  "mode": {
    "enum": [
      "SMART",
      "WORD",
      "STRICT"
    ],
    "default": "SMART"
  },
  "condition": {
    "enum": [
      "any",
      "all"
    ],
    "default": "any"
  }
}

Discover current catalog values

Enter a full API key with search scope. Lookup does not spend search or export credits. Browse starter values without typing, or enter at least 2 characters for large typeahead catalogs. Pages contain up to 100 values.

Your key stays in this page's memory and is sent only to the SearchLeads API. Manage API keys

Full API key

Company filter reference

LinkedIn URL — account.linkedin

Accepted type: Exact domain or URL. Send in: textFilters. string or string[] of exact domains or URLs. Send an exact domain, LinkedIn URL, or website URL. A valid request can return zero matches when the value is not in the dataset.

Include limit: 10000. Exclude limit: 10000. Units: None.

Search request

{
  "searchType": "company",
  "textFilters": {
    "account.linkedin": "https://www.linkedin.com/company/example"
  },
  "page": 0,
  "size": 3
}

Exclusion request

{
  "searchType": "company",
  "excludedFilters": {
    "account.linkedin": "https://www.linkedin.com/company/example"
  },
  "page": 0,
  "size": 3
}

Search request with matching rules

{
  "searchType": "company",
  "textFilters": {
    "account.linkedin": "https://www.linkedin.com/company/example"
  },
  "page": 0,
  "size": 3,
  "filterRules": {
    "account.linkedin": {
      "matchAll": false,
      "exclude": false
    }
  }
}

CSV mapping: linkedin. Use these exact CSV header keys to check the corresponding source value; missing values and exclusions follow the documented filter semantics.

Rule schema (reference only)

{
  "matchAll": {
    "type": "boolean",
    "default": false
  },
  "exclude": {
    "type": "boolean",
    "default": false
  },
  "condition": {
    "enum": [
      "any",
      "all"
    ],
    "default": "any"
  }
}

Industry — account.industry

Accepted type: Select exact catalog values. Send in: filters. string[] of exact current option IDs or readable labels. Call the filter-options option lookup, then submit exact options[].id or options[].label values. Do not invent catalog values.

Include limit: 300. Exclude limit: 300. Units: None.

Select an exact returned option ID or label to build a search request.

POST filter-options with a full API key with search scope:

{
  "searchType": "company",
  "field": "account.industry",
  "limit": 100
}

Merge this filterRules fragment into a search request after selecting a catalog value.

{
  "filterRules": {
    "account.industry": {
      "matchAll": false,
      "exclude": false
    }
  }
}

CSV mapping: industry. Use these exact CSV header keys to check the corresponding source value; missing values and exclusions follow the documented filter semantics.

Rule schema (reference only)

{
  "matchAll": {
    "type": "boolean",
    "default": false
  },
  "exclude": {
    "type": "boolean",
    "default": false
  },
  "condition": {
    "enum": [
      "any",
      "all"
    ],
    "default": "any"
  }
}

Employee Size — account.employeesize

Accepted type: Numeric range. Send in: filters. one object with min and/or max, or an array of those range objects. A single range object remains supported. Multiple Employee Count ranges are ORed; use grounded non-negative integer boundaries.

Include limit: 300. Exclude limit: 300. Units: count.

Search request

{
  "searchType": "company",
  "filters": {
    "account.employeesize": {
      "min": 1,
      "max": 100
    }
  },
  "page": 0,
  "size": 3
}

Exclusion request

{
  "searchType": "company",
  "excludedFilters": {
    "account.employeesize": {
      "min": 1,
      "max": 100
    }
  },
  "page": 0,
  "size": 3
}

Search request with matching rules

{
  "searchType": "company",
  "filters": {
    "account.employeesize": {
      "min": 1,
      "max": 100
    }
  },
  "page": 0,
  "size": 3,
  "filterRules": {
    "account.employeesize": {
      "matchAll": false,
      "exclude": false
    }
  }
}

CSV mapping: employees. Use these exact CSV header keys to check the corresponding source value; missing values and exclusions follow the documented filter semantics.

Rule schema (reference only)

{
  "matchAll": {
    "type": "boolean",
    "default": false
  },
  "exclude": {
    "type": "boolean",
    "default": false
  },
  "condition": {
    "enum": [
      "any",
      "all"
    ],
    "default": "any"
  }
}

Annual Revenue — account.revenue

Accepted type: Numeric range. Send in: filters. object with grounded min and/or max values. Send a range only when the prompt or campaign strategy gives a real reason for that constraint.

Include limit: 300. Exclude limit: 300. Units: USD.

Search request

{
  "searchType": "company",
  "filters": {
    "account.revenue": {
      "min": 1000000,
      "max": 10000000
    }
  },
  "page": 0,
  "size": 3
}

Exclusion request

{
  "searchType": "company",
  "excludedFilters": {
    "account.revenue": {
      "min": 1000000,
      "max": 10000000
    }
  },
  "page": 0,
  "size": 3
}

Search request with matching rules

{
  "searchType": "company",
  "filters": {
    "account.revenue": {
      "min": 1000000,
      "max": 10000000
    }
  },
  "page": 0,
  "size": 3,
  "filterRules": {
    "account.revenue": {
      "matchAll": false,
      "exclude": false
    }
  }
}

CSV mapping: revenue. Related CSV columns are listed. Matching can span multiple source fields, use fallback values or derived conditions; these columns alone do not prove every predicate.

Rule schema (reference only)

{
  "matchAll": {
    "type": "boolean",
    "default": false
  },
  "exclude": {
    "type": "boolean",
    "default": false
  },
  "condition": {
    "enum": [
      "any",
      "all"
    ],
    "default": "any"
  }
}

Company Type — account.type

Include limit: 300. Exclude limit: 300. Units: None.

Select an exact returned option ID or label to build a search request.

POST filter-options with a full API key with search scope:

{
  "searchType": "company",
  "field": "account.type",
  "limit": 100
}

Merge this filterRules fragment into a search request after selecting a catalog value.

{
  "filterRules": {
    "account.type": {
      "matchAll": false,
      "exclude": false
    }
  }
}

CSV mapping: companyType. Use these exact CSV header keys to check the corresponding source value; missing values and exclusions follow the documented filter semantics.

Rule schema (reference only)

{
  "matchAll": {
    "type": "boolean",
    "default": false
  },
  "exclude": {
    "type": "boolean",
    "default": false
  },
  "condition": {
    "enum": [
      "any",
      "all"
    ],
    "default": "any"
  }
}

Founded Year — account.foundedyear

Accepted type: Numeric range. Send in: filters. object with grounded min and/or max values. Send a range only when the prompt or campaign strategy gives a real reason for that constraint.

Include limit: 300. Exclude limit: 300. Units: year.

Search request

{
  "searchType": "company",
  "filters": {
    "account.foundedyear": {
      "min": 2010,
      "max": 2025
    }
  },
  "page": 0,
  "size": 3
}

Exclusion request

{
  "searchType": "company",
  "excludedFilters": {
    "account.foundedyear": {
      "min": 2010,
      "max": 2025
    }
  },
  "page": 0,
  "size": 3
}

Search request with matching rules

{
  "searchType": "company",
  "filters": {
    "account.foundedyear": {
      "min": 2010,
      "max": 2025
    }
  },
  "page": 0,
  "size": 3,
  "filterRules": {
    "account.foundedyear": {
      "matchAll": false,
      "exclude": false
    }
  }
}

CSV mapping: foundedYear. Use these exact CSV header keys to check the corresponding source value; missing values and exclusions follow the documented filter semantics.

Rule schema (reference only)

{
  "matchAll": {
    "type": "boolean",
    "default": false
  },
  "exclude": {
    "type": "boolean",
    "default": false
  },
  "condition": {
    "enum": [
      "any",
      "all"
    ],
    "default": "any"
  }
}

Technologies — account.technology

Include limit: 300. Exclude limit: 300. Units: None.

Select an exact returned option ID or label to build a search request.

POST filter-options with a full API key with search scope:

{
  "searchType": "company",
  "field": "account.technology",
  "limit": 100
}

Merge this filterRules fragment into a search request after selecting a catalog value.

{
  "filterRules": {
    "account.technology": {
      "matchAll": false,
      "exclude": false,
      "mode": "SMART"
    }
  }
}

CSV mapping: technologies. Related CSV columns are listed. Matching can span multiple source fields, use fallback values or derived conditions; these columns alone do not prove every predicate.

Rule schema (reference only)

{
  "matchAll": {
    "type": "boolean",
    "default": false
  },
  "exclude": {
    "type": "boolean",
    "default": false
  },
  "mode": {
    "enum": [
      "SMART",
      "WORD",
      "STRICT"
    ],
    "default": "SMART"
  },
  "condition": {
    "enum": [
      "any",
      "all"
    ],
    "default": "any"
  }
}

Headcount Growth — account.metric.growth

Accepted type: Numeric range. Send in: filters. object with grounded min and/or max values. Send a range only when the prompt or campaign strategy gives a real reason for that constraint.

Include limit: 300. Exclude limit: 300. Units: percent.

Search request

{
  "searchType": "company",
  "filters": {
    "account.metric.growth": {
      "min": 10,
      "max": 50
    }
  },
  "page": 0,
  "size": 3
}

Exclusion request

{
  "searchType": "company",
  "excludedFilters": {
    "account.metric.growth": {
      "min": 10,
      "max": 50
    }
  },
  "page": 0,
  "size": 3
}

Search request with matching rules

{
  "searchType": "company",
  "filters": {
    "account.metric.growth": {
      "min": 10,
      "max": 50
    }
  },
  "page": 0,
  "size": 3,
  "filterRules": {
    "account.metric.growth": {
      "min": 10,
      "max": 50
    }
  }
}

CSV mapping: headcountGrowth. Use these exact CSV header keys to check the corresponding source value; missing values and exclusions follow the documented filter semantics.

Rule schema (reference only)

{
  "min": {
    "type": "number"
  },
  "max": {
    "type": "number"
  }
}

NAICS — account.naics

Include limit: 300. Exclude limit: 300. Units: None.

Select an exact returned option ID or label to build a search request.

POST filter-options with a full API key with search scope:

{
  "searchType": "company",
  "field": "account.naics",
  "limit": 100
}

Merge this filterRules fragment into a search request after selecting a catalog value.

{
  "filterRules": {
    "account.naics": {
      "matchAll": false,
      "exclude": false
    }
  }
}

CSV mapping: naics. Use these exact CSV header keys to check the corresponding source value; missing values and exclusions follow the documented filter semantics.

Rule schema (reference only)

{
  "matchAll": {
    "type": "boolean",
    "default": false
  },
  "exclude": {
    "type": "boolean",
    "default": false
  },
  "condition": {
    "enum": [
      "any",
      "all"
    ],
    "default": "any"
  }
}

Keywords — account.keyword

Accepted type: Text values. Send in: textFilters. string or string[] of short keyword terms. Custom values are allowed, but keep them concise buyer-side terms. Do not send full prompts or sentences.

Include limit: 300. Exclude limit: 300. Units: None.

Search request

{
  "searchType": "company",
  "textFilters": {
    "account.keyword": "outbound sales"
  },
  "page": 0,
  "size": 3
}

Exclusion request

{
  "searchType": "company",
  "excludedFilters": {
    "account.keyword": "outbound sales"
  },
  "page": 0,
  "size": 3
}

Search request with matching rules

{
  "searchType": "company",
  "textFilters": {
    "account.keyword": "outbound sales"
  },
  "page": 0,
  "size": 3,
  "filterRules": {
    "account.keyword": {
      "matchAll": false,
      "exclude": false,
      "mode": "SMART"
    }
  }
}

CSV mapping: name, description, industry, technologies, companyKeywords. Related CSV columns are listed. Matching can span multiple source fields, use fallback values or derived conditions; these columns alone do not prove every predicate.

Rule schema (reference only)

{
  "matchAll": {
    "type": "boolean",
    "default": false
  },
  "exclude": {
    "type": "boolean",
    "default": false
  },
  "mode": {
    "enum": [
      "SMART",
      "WORD",
      "STRICT"
    ],
    "default": "SMART"
  },
  "condition": {
    "enum": [
      "any",
      "all"
    ],
    "default": "any"
  },
  "sources": {
    "type": "array",
    "items": {
      "enum": [
        "NAME",
        "DESCRIPTION",
        "SPECIALTIES",
        "INDUSTRY",
        "TECHNOLOGIES"
      ]
    }
  },
  "includeSources": {
    "type": "array",
    "items": {
      "enum": [
        "NAME",
        "DESCRIPTION",
        "SPECIALTIES",
        "INDUSTRY",
        "TECHNOLOGIES"
      ]
    }
  },
  "excludeSources": {
    "type": "array",
    "items": {
      "enum": [
        "NAME",
        "DESCRIPTION",
        "SPECIALTIES",
        "INDUSTRY",
        "TECHNOLOGIES"
      ]
    }
  }
}

Domain — account.domain

Include limit: 10000. Exclude limit: 10000. Units: None.

Search request

{
  "searchType": "company",
  "textFilters": {
    "account.domain": "example.com"
  },
  "page": 0,
  "size": 3
}

Exclusion request

{
  "searchType": "company",
  "excludedFilters": {
    "account.domain": "example.com"
  },
  "page": 0,
  "size": 3
}

Search request with matching rules

{
  "searchType": "company",
  "textFilters": {
    "account.domain": "example.com"
  },
  "page": 0,
  "size": 3,
  "filterRules": {
    "account.domain": {
      "matchAll": false,
      "exclude": false
    }
  }
}

CSV mapping: domain. Use these exact CSV header keys to check the corresponding source value; missing values and exclusions follow the documented filter semantics.

Rule schema (reference only)

{
  "matchAll": {
    "type": "boolean",
    "default": false
  },
  "exclude": {
    "type": "boolean",
    "default": false
  },
  "condition": {
    "enum": [
      "any",
      "all"
    ],
    "default": "any"
  }
}

Company Name — account.name

Include limit: 300. Exclude limit: 300. Units: None.

Select an exact returned option ID or label to build a search request.

POST filter-options with a full API key with search scope:

{
  "searchType": "company",
  "field": "account.name",
  "limit": 100
}

Merge this filterRules fragment into a search request after selecting a catalog value.

{
  "filterRules": {
    "account.name": {
      "matchAll": false,
      "exclude": false
    }
  }
}

CSV mapping: name. Use these exact CSV header keys to check the corresponding source value; missing values and exclusions follow the documented filter semantics.

Rule schema (reference only)

{
  "matchAll": {
    "type": "boolean",
    "default": false
  },
  "exclude": {
    "type": "boolean",
    "default": false
  },
  "condition": {
    "enum": [
      "any",
      "all"
    ],
    "default": "any"
  }
}

Company Location — account.location

Include limit: 300. Exclude limit: 300. Units: None.

Search request

{
  "searchType": "company",
  "filters": {
    "account.location": [
      "United States"
    ]
  },
  "page": 0,
  "size": 3
}

Exclusion request

{
  "searchType": "company",
  "excludedFilters": {
    "account.location": [
      "United States"
    ]
  },
  "page": 0,
  "size": 3
}

POST filter-options with a full API key with search scope:

{
  "searchType": "company",
  "field": "account.location",
  "limit": 100
}

Search request with matching rules

{
  "searchType": "company",
  "filters": {
    "account.location": [
      "United States"
    ]
  },
  "page": 0,
  "size": 3,
  "filterRules": {
    "account.location": {
      "matchAll": false,
      "exclude": false
    }
  }
}

CSV mapping: location, city, state, country. Related CSV columns are listed. Matching can span multiple source fields, use fallback values or derived conditions; these columns alone do not prove every predicate.

Rule schema (reference only)

{
  "matchAll": {
    "type": "boolean",
    "default": false
  },
  "exclude": {
    "type": "boolean",
    "default": false
  },
  "condition": {
    "enum": [
      "any",
      "all"
    ],
    "default": "any"
  }
}

Employees by Department — account.metric.employee

Accepted type: Select a dimension and enter numeric bounds. Send in: filters. object or object[] with function, department, or role plus min and/or max. Choose an exact metric dimension from lookup_filter_options, then send that value as function (or department/role) with a grounded min and/or max. A bare { min, max } object is invalid because it does not identify a metric dimension.

Include limit: 300. Exclude limit: 300. Units: count.

Search request

{
  "searchType": "company",
  "filters": {
    "account.metric.employee": [
      {
        "function": "sales",
        "min": 1,
        "max": 10
      }
    ]
  },
  "page": 0,
  "size": 3
}

Exclusion request

{
  "searchType": "company",
  "excludedFilters": {
    "account.metric.employee": [
      {
        "function": "sales",
        "min": 1,
        "max": 10
      }
    ]
  },
  "page": 0,
  "size": 3
}

POST filter-options with a full API key with search scope:

{
  "searchType": "company",
  "field": "account.metric.employee",
  "limit": 100
}

Search request with matching rules

{
  "searchType": "company",
  "filters": {
    "account.metric.employee": [
      {
        "function": "sales",
        "min": 1,
        "max": 10
      }
    ]
  },
  "page": 0,
  "size": 3,
  "filterRules": {
    "account.metric.employee": {
      "matchAll": false,
      "metricRows": [
        {
          "functions": [
            "sales"
          ],
          "start": 1,
          "end": 10,
          "exclude": false
        }
      ]
    }
  }
}

CSV mapping: departmentEmployees. Related CSV columns are listed. Matching can span multiple source fields, use fallback values or derived conditions; these columns alone do not prove every predicate.

Rule schema (reference only)

{
  "matchAll": {
    "type": "boolean",
    "default": false
  },
  "metricRows": {
    "type": "array",
    "items": {
      "type": "object",
      "properties": {
        "functions": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "description": "Exact dimensions returned by this field's filter-options lookup."
        },
        "start": {
          "type": "number"
        },
        "end": {
          "type": "number"
        },
        "exclude": {
          "type": "boolean",
          "default": false
        }
      }
    }
  }
}

Hiring & Open Roles — account.hiring

Include limit: 300. Exclude limit: 300. Units: None.

Select an exact returned option ID or label to build a search request.

POST filter-options with a full API key with search scope:

{
  "searchType": "company",
  "field": "account.hiring",
  "limit": 100
}

Merge this filterRules fragment into a search request after selecting a catalog value.

{
  "filterRules": {
    "account.hiring": {
      "matchAll": false,
      "exclude": false
    }
  }
}

CSV mapping: No direct column. No direct CSV column exposes this predicate. Verify the applied query and source data; a missing column does not mean the filter was ignored.

Rule schema (reference only)

{
  "matchAll": {
    "type": "boolean",
    "default": false
  },
  "exclude": {
    "type": "boolean",
    "default": false
  },
  "condition": {
    "enum": [
      "any",
      "all"
    ],
    "default": "any"
  }
}

Open Roles — account.openroles

Include limit: 300. Exclude limit: 300. Units: count.

Search request

{
  "searchType": "company",
  "filters": {
    "account.openroles": [
      {
        "function": "sales",
        "min": 1,
        "max": 10
      }
    ]
  },
  "page": 0,
  "size": 3
}

Exclusion request

{
  "searchType": "company",
  "excludedFilters": {
    "account.openroles": [
      {
        "function": "sales",
        "min": 1,
        "max": 10
      }
    ]
  },
  "page": 0,
  "size": 3
}

POST filter-options with a full API key with search scope:

{
  "searchType": "company",
  "field": "account.openroles",
  "limit": 100
}

Search request with matching rules

{
  "searchType": "company",
  "filters": {
    "account.openroles": [
      {
        "function": "sales",
        "min": 1,
        "max": 10
      }
    ]
  },
  "page": 0,
  "size": 3,
  "filterRules": {
    "account.openroles": {
      "matchAll": false,
      "metricRows": [
        {
          "functions": [
            "sales"
          ],
          "start": 1,
          "end": 10,
          "exclude": false
        }
      ]
    }
  }
}

CSV mapping: hiringDepartments, openRoles. Related CSV columns are listed. Matching can span multiple source fields, use fallback values or derived conditions; these columns alone do not prove every predicate.

Rule schema (reference only)

{
  "matchAll": {
    "type": "boolean",
    "default": false
  },
  "metricRows": {
    "type": "array",
    "items": {
      "type": "object",
      "properties": {
        "functions": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "description": "Exact dimensions returned by this field's filter-options lookup."
        },
        "start": {
          "type": "number"
        },
        "end": {
          "type": "number"
        },
        "exclude": {
          "type": "boolean",
          "default": false
        }
      }
    }
  }
}

Has Funding Data — account.funding.available

Accepted type: Yes / No (true / false). Send in: filters. boolean, "true"/"false", or an array containing one of those values. Send true or false (or the string "true"/"false"). No catalog lookup is needed.

Include limit: 1. Exclude limit: 1. Units: None.

Search request

{
  "searchType": "company",
  "filters": {
    "account.funding.available": [
      "true"
    ]
  },
  "page": 0,
  "size": 3
}

Exclusion request

{
  "searchType": "company",
  "excludedFilters": {
    "account.funding.available": [
      "true"
    ]
  },
  "page": 0,
  "size": 3
}

Search request with matching rules

{
  "searchType": "company",
  "filters": {
    "account.funding.available": [
      "true"
    ]
  },
  "page": 0,
  "size": 3,
  "filterRules": {
    "account.funding.available": {
      "matchAll": false,
      "exclude": false
    }
  }
}

CSV mapping: lastFundingType. Related CSV columns are listed. Matching can span multiple source fields, use fallback values or derived conditions; these columns alone do not prove every predicate.

Rule schema (reference only)

{
  "matchAll": {
    "type": "boolean",
    "default": false
  },
  "exclude": {
    "type": "boolean",
    "default": false
  },
  "condition": {
    "enum": [
      "any",
      "all"
    ],
    "default": "any"
  }
}

Last Funding Type — account.funding.lasttype

Include limit: 50. Exclude limit: 50. Units: None.

Select an exact returned option ID or label to build a search request.

POST filter-options with a full API key with search scope:

{
  "searchType": "company",
  "field": "account.funding.lasttype",
  "limit": 100
}

Merge this filterRules fragment into a search request after selecting a catalog value.

{
  "filterRules": {
    "account.funding.lasttype": {
      "matchAll": false,
      "exclude": false
    }
  }
}

CSV mapping: lastFundingType. Use these exact CSV header keys to check the corresponding source value; missing values and exclusions follow the documented filter semantics.

Rule schema (reference only)

{
  "matchAll": {
    "type": "boolean",
    "default": false
  },
  "exclude": {
    "type": "boolean",
    "default": false
  },
  "condition": {
    "enum": [
      "any",
      "all"
    ],
    "default": "any"
  }
}

Last Funding Amount — account.funding.lastamount

Accepted type: Numeric range. Send in: filters. object with grounded min and/or max values. Send a range only when the prompt or campaign strategy gives a real reason for that constraint.

Include limit: 20. Exclude limit: 20. Units: USD.

Search request

{
  "searchType": "company",
  "filters": {
    "account.funding.lastamount": {
      "min": 1000000,
      "max": 10000000
    }
  },
  "page": 0,
  "size": 3
}

Exclusion request

{
  "searchType": "company",
  "excludedFilters": {
    "account.funding.lastamount": {
      "min": 1000000,
      "max": 10000000
    }
  },
  "page": 0,
  "size": 3
}

Search request with matching rules

{
  "searchType": "company",
  "filters": {
    "account.funding.lastamount": {
      "min": 1000000,
      "max": 10000000
    }
  },
  "page": 0,
  "size": 3,
  "filterRules": {
    "account.funding.lastamount": {
      "matchAll": false,
      "exclude": false
    }
  }
}

CSV mapping: lastFundingAmount. Use these exact CSV header keys to check the corresponding source value; missing values and exclusions follow the documented filter semantics.

Rule schema (reference only)

{
  "matchAll": {
    "type": "boolean",
    "default": false
  },
  "exclude": {
    "type": "boolean",
    "default": false
  },
  "condition": {
    "enum": [
      "any",
      "all"
    ],
    "default": "any"
  }
}

Total Funding — account.funding.totalamount

Accepted type: Numeric range. Send in: filters. object with grounded min and/or max values. Send a range only when the prompt or campaign strategy gives a real reason for that constraint.

Include limit: 20. Exclude limit: 20. Units: USD.

Search request

{
  "searchType": "company",
  "filters": {
    "account.funding.totalamount": {
      "min": 1000000,
      "max": 10000000
    }
  },
  "page": 0,
  "size": 3
}

Exclusion request

{
  "searchType": "company",
  "excludedFilters": {
    "account.funding.totalamount": {
      "min": 1000000,
      "max": 10000000
    }
  },
  "page": 0,
  "size": 3
}

Search request with matching rules

{
  "searchType": "company",
  "filters": {
    "account.funding.totalamount": {
      "min": 1000000,
      "max": 10000000
    }
  },
  "page": 0,
  "size": 3,
  "filterRules": {
    "account.funding.totalamount": {
      "matchAll": false,
      "exclude": false
    }
  }
}

CSV mapping: totalFunding. Use these exact CSV header keys to check the corresponding source value; missing values and exclusions follow the documented filter semantics.

Rule schema (reference only)

{
  "matchAll": {
    "type": "boolean",
    "default": false
  },
  "exclude": {
    "type": "boolean",
    "default": false
  },
  "condition": {
    "enum": [
      "any",
      "all"
    ],
    "default": "any"
  }
}

Last Funding Date — account.funding.lastdate

Accepted type: Calendar date range. Send in: filters. object with ISO 8601 min and/or max dates (YYYY-MM-DD). Send ISO 8601 calendar dates as min and/or max; do not use numeric timestamps.

Include limit: 20. Exclude limit: 20. Units: ISO 8601 date (YYYY-MM-DD).

Search request

{
  "searchType": "company",
  "filters": {
    "account.funding.lastdate": {
      "min": "2024-01-01",
      "max": "2026-01-01"
    }
  },
  "page": 0,
  "size": 3
}

Exclusion request

{
  "searchType": "company",
  "excludedFilters": {
    "account.funding.lastdate": {
      "min": "2024-01-01",
      "max": "2026-01-01"
    }
  },
  "page": 0,
  "size": 3
}

Search request with matching rules

{
  "searchType": "company",
  "filters": {
    "account.funding.lastdate": {
      "min": "2024-01-01",
      "max": "2026-01-01"
    }
  },
  "page": 0,
  "size": 3,
  "filterRules": {
    "account.funding.lastdate": {
      "matchAll": false,
      "exclude": false
    }
  }
}

CSV mapping: lastFundingDate. Use these exact CSV header keys to check the corresponding source value; missing values and exclusions follow the documented filter semantics.

Rule schema (reference only)

{
  "matchAll": {
    "type": "boolean",
    "default": false
  },
  "exclude": {
    "type": "boolean",
    "default": false
  },
  "condition": {
    "enum": [
      "any",
      "all"
    ],
    "default": "any"
  }
}

Lead Investors — account.funding.leadinvestors

Include limit: 100. Exclude limit: 100. Units: None.

Select an exact returned option ID or label to build a search request.

POST filter-options with a full API key with search scope:

{
  "searchType": "company",
  "field": "account.funding.leadinvestors",
  "limit": 100
}

Merge this filterRules fragment into a search request after selecting a catalog value.

{
  "filterRules": {
    "account.funding.leadinvestors": {
      "matchAll": false,
      "exclude": false
    }
  }
}

CSV mapping: leadInvestors. Use these exact CSV header keys to check the corresponding source value; missing values and exclusions follow the documented filter semantics.

Rule schema (reference only)

{
  "matchAll": {
    "type": "boolean",
    "default": false
  },
  "exclude": {
    "type": "boolean",
    "default": false
  },
  "condition": {
    "enum": [
      "any",
      "all"
    ],
    "default": "any"
  }
}

Investor Count — account.funding.investorcount

Accepted type: Numeric range. Send in: filters. object with grounded min and/or max values. Send a range only when the prompt or campaign strategy gives a real reason for that constraint.

Include limit: 20. Exclude limit: 20. Units: count.

Search request

{
  "searchType": "company",
  "filters": {
    "account.funding.investorcount": {
      "min": 1,
      "max": 100
    }
  },
  "page": 0,
  "size": 3
}

Exclusion request

{
  "searchType": "company",
  "excludedFilters": {
    "account.funding.investorcount": {
      "min": 1,
      "max": 100
    }
  },
  "page": 0,
  "size": 3
}

Search request with matching rules

{
  "searchType": "company",
  "filters": {
    "account.funding.investorcount": {
      "min": 1,
      "max": 100
    }
  },
  "page": 0,
  "size": 3,
  "filterRules": {
    "account.funding.investorcount": {
      "matchAll": false,
      "exclude": false
    }
  }
}

CSV mapping: investorCount. Use these exact CSV header keys to check the corresponding source value; missing values and exclusions follow the documented filter semantics.

Rule schema (reference only)

{
  "matchAll": {
    "type": "boolean",
    "default": false
  },
  "exclude": {
    "type": "boolean",
    "default": false
  },
  "condition": {
    "enum": [
      "any",
      "all"
    ],
    "default": "any"
  }
}

Has CIO — account.hascio

Include limit: 300. Exclude limit: 300. Units: None.

Search request

{
  "searchType": "company",
  "filters": {
    "account.hascio": [
      "true"
    ]
  },
  "page": 0,
  "size": 3
}

Exclusion request

{
  "searchType": "company",
  "excludedFilters": {
    "account.hascio": [
      "true"
    ]
  },
  "page": 0,
  "size": 3
}

Search request with matching rules

{
  "searchType": "company",
  "filters": {
    "account.hascio": [
      "true"
    ]
  },
  "page": 0,
  "size": 3,
  "filterRules": {
    "account.hascio": {
      "matchAll": false,
      "exclude": false
    }
  }
}

CSV mapping: hasCio. Use these exact CSV header keys to check the corresponding source value; missing values and exclusions follow the documented filter semantics.

Rule schema (reference only)

{
  "matchAll": {
    "type": "boolean",
    "default": false
  },
  "exclude": {
    "type": "boolean",
    "default": false
  },
  "condition": {
    "enum": [
      "any",
      "all"
    ],
    "default": "any"
  }
}

Has CISO — account.hasciso

Include limit: 300. Exclude limit: 300. Units: None.

Search request

{
  "searchType": "company",
  "filters": {
    "account.hasciso": [
      "true"
    ]
  },
  "page": 0,
  "size": 3
}

Exclusion request

{
  "searchType": "company",
  "excludedFilters": {
    "account.hasciso": [
      "true"
    ]
  },
  "page": 0,
  "size": 3
}

Search request with matching rules

{
  "searchType": "company",
  "filters": {
    "account.hasciso": [
      "true"
    ]
  },
  "page": 0,
  "size": 3,
  "filterRules": {
    "account.hasciso": {
      "matchAll": false,
      "exclude": false
    }
  }
}

CSV mapping: hasCiso. Use these exact CSV header keys to check the corresponding source value; missing values and exclusions follow the documented filter semantics.

Rule schema (reference only)

{
  "matchAll": {
    "type": "boolean",
    "default": false
  },
  "exclude": {
    "type": "boolean",
    "default": false
  },
  "condition": {
    "enum": [
      "any",
      "all"
    ],
    "default": "any"
  }
}

Number of Locations — account.locationcount

Accepted type: Numeric range. Send in: filters. object with grounded min and/or max values. Send a range only when the prompt or campaign strategy gives a real reason for that constraint.

Include limit: 300. Exclude limit: 300. Units: count.

Search request

{
  "searchType": "company",
  "filters": {
    "account.locationcount": {
      "min": 1,
      "max": 100
    }
  },
  "page": 0,
  "size": 3
}

Exclusion request

{
  "searchType": "company",
  "excludedFilters": {
    "account.locationcount": {
      "min": 1,
      "max": 100
    }
  },
  "page": 0,
  "size": 3
}

Search request with matching rules

{
  "searchType": "company",
  "filters": {
    "account.locationcount": {
      "min": 1,
      "max": 100
    }
  },
  "page": 0,
  "size": 3,
  "filterRules": {
    "account.locationcount": {
      "matchAll": false,
      "exclude": false
    }
  }
}

CSV mapping: locationCount. Use these exact CSV header keys to check the corresponding source value; missing values and exclusions follow the documented filter semantics.

Rule schema (reference only)

{
  "matchAll": {
    "type": "boolean",
    "default": false
  },
  "exclude": {
    "type": "boolean",
    "default": false
  },
  "condition": {
    "enum": [
      "any",
      "all"
    ],
    "default": "any"
  }
}

Organic Traffic — account.organictraffic

Accepted type: Numeric range. Send in: filters. object with grounded min and/or max values. Send a range only when the prompt or campaign strategy gives a real reason for that constraint.

Include limit: 300. Exclude limit: 300. Units: count.

Search request

{
  "searchType": "company",
  "filters": {
    "account.organictraffic": {
      "min": 1,
      "max": 100
    }
  },
  "page": 0,
  "size": 3
}

Exclusion request

{
  "searchType": "company",
  "excludedFilters": {
    "account.organictraffic": {
      "min": 1,
      "max": 100
    }
  },
  "page": 0,
  "size": 3
}

Search request with matching rules

{
  "searchType": "company",
  "filters": {
    "account.organictraffic": {
      "min": 1,
      "max": 100
    }
  },
  "page": 0,
  "size": 3,
  "filterRules": {
    "account.organictraffic": {
      "matchAll": false,
      "exclude": false
    }
  }
}

CSV mapping: organicTraffic. Use these exact CSV header keys to check the corresponding source value; missing values and exclusions follow the documented filter semantics.

Rule schema (reference only)

{
  "matchAll": {
    "type": "boolean",
    "default": false
  },
  "exclude": {
    "type": "boolean",
    "default": false
  },
  "condition": {
    "enum": [
      "any",
      "all"
    ],
    "default": "any"
  }
}

Paid Traffic — account.paidtraffic

Accepted type: Numeric range. Send in: filters. object with grounded min and/or max values. Send a range only when the prompt or campaign strategy gives a real reason for that constraint.

Include limit: 300. Exclude limit: 300. Units: count.

Search request

{
  "searchType": "company",
  "filters": {
    "account.paidtraffic": {
      "min": 1,
      "max": 100
    }
  },
  "page": 0,
  "size": 3
}

Exclusion request

{
  "searchType": "company",
  "excludedFilters": {
    "account.paidtraffic": {
      "min": 1,
      "max": 100
    }
  },
  "page": 0,
  "size": 3
}

Search request with matching rules

{
  "searchType": "company",
  "filters": {
    "account.paidtraffic": {
      "min": 1,
      "max": 100
    }
  },
  "page": 0,
  "size": 3,
  "filterRules": {
    "account.paidtraffic": {
      "matchAll": false,
      "exclude": false
    }
  }
}

CSV mapping: paidTraffic. Use these exact CSV header keys to check the corresponding source value; missing values and exclusions follow the documented filter semantics.

Rule schema (reference only)

{
  "matchAll": {
    "type": "boolean",
    "default": false
  },
  "exclude": {
    "type": "boolean",
    "default": false
  },
  "condition": {
    "enum": [
      "any",
      "all"
    ],
    "default": "any"
  }
}

SIC Codes — account.sic

Include limit: 300. Exclude limit: 300. Units: None.

Select an exact returned option ID or label to build a search request.

POST filter-options with a full API key with search scope:

{
  "searchType": "company",
  "field": "account.sic",
  "limit": 100
}

Merge this filterRules fragment into a search request after selecting a catalog value.

{
  "filterRules": {
    "account.sic": {
      "matchAll": false,
      "exclude": false
    }
  }
}

CSV mapping: sicCodes. Use these exact CSV header keys to check the corresponding source value; missing values and exclusions follow the documented filter semantics.

Rule schema (reference only)

{
  "matchAll": {
    "type": "boolean",
    "default": false
  },
  "exclude": {
    "type": "boolean",
    "default": false
  },
  "condition": {
    "enum": [
      "any",
      "all"
    ],
    "default": "any"
  }
}

Legal Structure — account.legaltype

Include limit: 300. Exclude limit: 300. Units: None.

Select an exact returned option ID or label to build a search request.

POST filter-options with a full API key with search scope:

{
  "searchType": "company",
  "field": "account.legaltype",
  "limit": 100
}

Merge this filterRules fragment into a search request after selecting a catalog value.

{
  "filterRules": {
    "account.legaltype": {
      "matchAll": false,
      "exclude": false
    }
  }
}

CSV mapping: legalType, companyType. Use these exact CSV header keys to check the corresponding source value; missing values and exclusions follow the documented filter semantics.

Rule schema (reference only)

{
  "matchAll": {
    "type": "boolean",
    "default": false
  },
  "exclude": {
    "type": "boolean",
    "default": false
  },
  "condition": {
    "enum": [
      "any",
      "all"
    ],
    "default": "any"
  }
}

Website for Sale — account.websiteforsale

Include limit: 300. Exclude limit: 300. Units: None.

Search request

{
  "searchType": "company",
  "filters": {
    "account.websiteforsale": [
      "true"
    ]
  },
  "page": 0,
  "size": 3
}

Exclusion request

{
  "searchType": "company",
  "excludedFilters": {
    "account.websiteforsale": [
      "true"
    ]
  },
  "page": 0,
  "size": 3
}

Search request with matching rules

{
  "searchType": "company",
  "filters": {
    "account.websiteforsale": [
      "true"
    ]
  },
  "page": 0,
  "size": 3,
  "filterRules": {
    "account.websiteforsale": {
      "matchAll": false,
      "exclude": false
    }
  }
}

CSV mapping: websiteForSale. Use these exact CSV header keys to check the corresponding source value; missing values and exclusions follow the documented filter semantics.

Rule schema (reference only)

{
  "matchAll": {
    "type": "boolean",
    "default": false
  },
  "exclude": {
    "type": "boolean",
    "default": false
  },
  "condition": {
    "enum": [
      "any",
      "all"
    ],
    "default": "any"
  }
}

Working Website — account.websiteworking

Include limit: 300. Exclude limit: 300. Units: None.

Search request

{
  "searchType": "company",
  "filters": {
    "account.websiteworking": [
      "true"
    ]
  },
  "page": 0,
  "size": 3
}

Exclusion request

{
  "searchType": "company",
  "excludedFilters": {
    "account.websiteworking": [
      "true"
    ]
  },
  "page": 0,
  "size": 3
}

Search request with matching rules

{
  "searchType": "company",
  "filters": {
    "account.websiteworking": [
      "true"
    ]
  },
  "page": 0,
  "size": 3,
  "filterRules": {
    "account.websiteworking": {
      "matchAll": false,
      "exclude": false
    }
  }
}

CSV mapping: websiteWorking. Use these exact CSV header keys to check the corresponding source value; missing values and exclusions follow the documented filter semantics.

Rule schema (reference only)

{
  "matchAll": {
    "type": "boolean",
    "default": false
  },
  "exclude": {
    "type": "boolean",
    "default": false
  },
  "condition": {
    "enum": [
      "any",
      "all"
    ],
    "default": "any"
  }
}

Company LinkedIn Followers — account.linkedinfollowers

Accepted type: Numeric range. Send in: filters. object with grounded min and/or max values. Send a range only when the prompt or campaign strategy gives a real reason for that constraint.

Include limit: 300. Exclude limit: 300. Units: count.

Search request

{
  "searchType": "company",
  "filters": {
    "account.linkedinfollowers": {
      "min": 1,
      "max": 100
    }
  },
  "page": 0,
  "size": 3
}

Exclusion request

{
  "searchType": "company",
  "excludedFilters": {
    "account.linkedinfollowers": {
      "min": 1,
      "max": 100
    }
  },
  "page": 0,
  "size": 3
}

Search request with matching rules

{
  "searchType": "company",
  "filters": {
    "account.linkedinfollowers": {
      "min": 1,
      "max": 100
    }
  },
  "page": 0,
  "size": 3,
  "filterRules": {
    "account.linkedinfollowers": {
      "matchAll": false,
      "exclude": false
    }
  }
}

CSV mapping: linkedinFollowers. Use these exact CSV header keys to check the corresponding source value; missing values and exclusions follow the documented filter semantics.

Rule schema (reference only)

{
  "matchAll": {
    "type": "boolean",
    "default": false
  },
  "exclude": {
    "type": "boolean",
    "default": false
  },
  "condition": {
    "enum": [
      "any",
      "all"
    ],
    "default": "any"
  }
}

UK SIC Codes — account.uksic

Include limit: 300. Exclude limit: 300. Units: None.

Select an exact returned option ID or label to build a search request.

POST filter-options with a full API key with search scope:

{
  "searchType": "company",
  "field": "account.uksic",
  "limit": 100
}

Merge this filterRules fragment into a search request after selecting a catalog value.

{
  "filterRules": {
    "account.uksic": {
      "matchAll": false,
      "exclude": false
    }
  }
}

CSV mapping: ukSicCodes. Use these exact CSV header keys to check the corresponding source value; missing values and exclusions follow the documented filter semantics.

Rule schema (reference only)

{
  "matchAll": {
    "type": "boolean",
    "default": false
  },
  "exclude": {
    "type": "boolean",
    "default": false
  },
  "condition": {
    "enum": [
      "any",
      "all"
    ],
    "default": "any"
  }
}

Filters and option discovery

Browsing and query-required optionsCopy Anchor Link

Company signals and export mappingsCopy Anchor Link

Value rulesCopy Anchor Link

Option paginationCopy Anchor Link

Quick valuesCopy Anchor Link

Complete filter referenceCopy Anchor Link

Live filter reference

Discover current catalog values

On this page

Browsing and query-required options

Company signals and export mappings

Value rules

Option pagination

Quick values

Complete filter reference