ICP Search Filter Reference

All filter values are human-readable strings — no internal IDs required. Pass them directly in your search request. Use GET /api/v1/people-search/filters to retrieve all valid values at once — useful for populating dropdowns. No credits consumed.

curl https://api.datamagnet.co/api/v1/people-search/filters \
  -H "Authorization: Bearer <your_api_key>"

Filters come in two kinds, and /people-search/filters reports both.Closed vocabularies — seniority, headcount, company type, function, industry and the rest — have a fixed set of values, listed under filters. Pick from those exactly.Free-text filters — location, job_title, company_name, school, technology — are resolved from whatever string you send, so they have no value list. They are listed under filters.dynamic_fields with a description instead of values. Use /people-search/suggest to preview how a given string will resolve.

Seniority level

Filter people by their seniority level in the organization.

Value	Aliases
`Owner`
`Partner`
`CXO`	`C-Level`
`Vice President`	`VP`
`Director`
`Experienced Manager`	`Manager`
`Entry Level Manager`
`Strategic`
`Senior`
`Entry Level`
`In Training`	`Intern`

Example:

{ "seniority": ["CXO", "Vice President", "Director"] }

Company headcount

Filter by the number of employees at the company.

Value
`Self-Employed`
`1-10`
`11-50`
`51-200`
`201-500`
`501-1,000`
`1,001-5,000`
`5,001-10,000`
`10,001+`

Example:

{ "company_headcount": ["501-1,000", "1,001-5,000"] }

Company type

Value	Aliases
`Public`	`Public Company`
`Private`	`Privately Held`
`Non Profit`	`Nonprofit`
`Educational`	`Educational Institution`
`Partnership`
`Self Employed`
`Government`	`Government Agency`

Example:

{ "company_type": "Public" }

Company name

Pass any company name as a string. Accepts a single value or an array. Example:

{ "company_name": "Stripe" }

{ "company_name": ["Stripe", "Plaid"] }

Job title

Pass any job title as a string. Accepts a single value or an array. Example:

{ "job_title": "CTO" }

{ "job_title": ["CTO", "Chief Technology Officer"] }

Location

City, region, or country. Accepts a single value or an array. Example:

{ "location": "San Francisco" }

{ "location": ["San Francisco", "New York", "London"] }

Industry

Over 300 industries are supported. Values are case-insensitive and partial matching is supported (e.g. "software" matches "Software Development"). Use GET /api/v1/people-search/filters to get the full sorted list. Sample values:

Software Development, Financial Services, Healthcare, Manufacturing,
Retail, Education, Real Estate, Consulting, Marketing Services,
IT Services and IT Consulting, Banking, Insurance, ...

Example:

{ "industry": "Software Development" }

School

University or school name. Accepts a single value or an array. Example:

{ "school": "MIT" }

Technology

Technologies used by the person’s company. Accepts a single value or an array. Example:

{ "technology": ["Salesforce", "HubSpot"] }

Function / department

Filter by the person’s functional department.

Value
`Accounting`
`Administrative`
`Arts and Design`
`Business Development`
`Consulting`
`Customer Success`
`Education`
`Engineering`
`Entrepreneurship`
`Finance`
`Healthcare`
`Human Resources`
`Information Technology`
`Legal`
`Marketing`
`Media`
`Military`
`Operations`
`Product Management`
`Program Management`
`Purchasing`
`Quality Assurance`
`Real Estate`
`Research`
`Sales`
`Support`

Example:

{ "function": ["Engineering", "Product Management"] }

Years in current position

Value	Aliases
`Less than 1 year`	`<1`
`1 to 2 years`	`1-2`
`3 to 5 years`	`3-5`
`6 to 10 years`	`6-10`
`More than 10 years`	`10+`

Example:

{ "years_in_position": "1 to 2 years" }

Followers count

Filter by the number of LinkedIn followers.

Value
`1-50`
`51-100`
`101-1000`
`1001-5000`
`5001+`

Example:

{ "followers_count": "1001-5000" }

Recent activities

Filter by recent company activity signals.

Value	Aliases
`Funding`	`Funding Events`
`Leadership Changes`	`Senior Leadership Changes`

Example:

{ "recent_activities": "Funding" }

Job opportunities

Filter to companies actively hiring.

Value
`Hiring`

Example:

{ "job_opportunities": "Hiring" }

Recently changed jobs

Sales Navigator’s Changed jobs spotlight: people who recently started a new position. LinkedIn decides what counts as recent — the filter carries no date range of its own. It is a single checkbox in Sales Navigator, so it has one value.

Value	Aliases
`Changed Jobs`	`Recently Changed Jobs`, `Job Change`

Example:

{ "recently_changed_jobs": "Changed Jobs" }

A boolean works too, which usually reads better for a one-value filter:

{ "recently_changed_jobs": true }

false means do not filter on this and is the same as leaving the field out — not “people who have not changed jobs”. Sales Navigator offers this spotlight as an include-only checkbox, so there is no tested way to ask for the opposite.

Combine it with the filters that describe who you are looking for:

{
  "recently_changed_jobs": true,
  "seniority": ["CXO", "Owner", "Vice President"],
  "company_headcount": ["1-10", "11-50"],
  "industry": "Telecommunications",
  "location": "United States"
}

Posted on LinkedIn

Sales Navigator’s Posted on LinkedIn spotlight: people who have recently posted on LinkedIn. LinkedIn decides what counts as recent — the filter carries no date range of its own. Like Changed jobs, it is a single checkbox in Sales Navigator with one value.

Value	Aliases
`Posted on LinkedIn`	`Recently Posted`, `Posted Recently`

Example:

{ "posted_on_linkedin": true }

false means do not filter on this and is the same as leaving the field out — not “people who have not posted”. Sales Navigator offers this spotlight as an include-only checkbox, so there is no tested way to ask for the opposite.

It combines with the other filters, including Changed jobs:

{
  "posted_on_linkedin": true,
  "seniority": ["CXO", "Owner", "Vice President"],
  "company_headcount": ["1-10", "11-50"],
  "industry": "Telecommunications",
  "location": "United States"
}

Profile language

Filter by the language the person’s profile is written in.

Value	Value	Value
`Arabic`	`English`	`Spanish`
`Portuguese`	`Chinese`	`French`
`Italian`	`Russian`	`German`
`Dutch`	`Turkish`	`Tagalog`
`Polish`	`Korean`	`Japanese`
`Malay`	`Norwegian`	`Danish`
`Romanian`	`Swedish`	`Indonesian`
`Czech`

Example:

{ "profile_language": "English" }

Include / exclude syntax

Every filter supports negative matching. To exclude a value, wrap it in an object with "exclude": true:

{
  "company_name": [
    "Stripe",
    { "value": "PayPal", "exclude": true }
  ]
}

This returns people who work at Stripe but not PayPal. Explicit form using selection:

{ "value": "PayPal", "selection": "EXCLUDED" }

Getting Started

Concepts

ICP Search — Filter Reference

ICP Search Filter Reference

Seniority level

Company headcount

Company type

Company name

Job title

Location

Industry

School

Technology

Function / department

Years in current position

Followers count

Recent activities

Job opportunities

Recently changed jobs

Posted on LinkedIn

Profile language

Include / exclude syntax

​ICP Search Filter Reference

​Seniority level

​Company headcount

​Company type

​Company name

​Job title

​Location

​Industry

​School

​Technology

​Function / department

​Years in current position

​Followers count

​Recent activities

​Job opportunities

​Recently changed jobs

​Posted on LinkedIn

​Profile language

​Include / exclude syntax

ICP Search Filter Reference

Seniority level

Company headcount

Company type

Company name

Job title

Location

Industry

School

Technology

Function / department

Years in current position

Followers count

Recent activities

Job opportunities

Recently changed jobs

Posted on LinkedIn

Profile language

Include / exclude syntax