Skip to main content
Filter Search returns the people or companies that match exact conditions on indexed fields. Use it when you know the fields and values you want. To describe who you need in words, use Deep Search.

Build a filter

  1. List the fields you can filter on with GET /v1/people/search/fields or GET /v1/companies/search/fields. Field names differ between people and companies.
  2. Look up the values a field holds with POST /v1/people/search/field-values. A filter on a value that is spelled differently in the index matches nothing.
  3. Write the filter in one of two formats, and send it as filters.

Request

This request uses a DSL filter to find people who work at Sixtyfour now.

Response

Returns a Job. Read the finished profiles from GET /v1/jobs/{job_id}/items.
Item response
Person profile keys use camelCase, such as fullName and linkedinUrl. Each item repeats the retained search parameters in input.

Parameters

object
required
Exact, range or Boolean conditions, as simple filters or DSL filters.
A search takes exactly one of filters, query, seeds or search_id. See Deep Search for the others.
integer
default:10
Maximum results. Minimum 1, up to the max_results returned by GET /v1/people/search/fields or GET /v1/companies/search/fields.
string[]
Saved lists to leave out. Limit: 5 by default, up to 10 with a higher organization limit.
integer
default:5
Seconds to wait for the Job to finish, from 0 to 20.
string
HTTPS callback URL. See Outgoing Webhooks.

Discover fields

Read GET /v1/people/search/fields or GET /v1/companies/search/fields before building filters. Each field describes its supported operators and value type.

Field entry

Each item in fields describes one queryable field. To list fields by property, filter the fields response, for example with jq '.fields[] | select(.supports_top_values) | .field'.

Field values

Use POST /v1/people/search/field-values or POST /v1/companies/search/field-values to list common values before building a filter.

Response fields

Nested fields

For nested fields such as technologies_used.technology, counts are record counts, and each filter_snippet is wrapped in a nested clause, ready to use in filters.

Simple filters

Place field names directly under filters. Use the people route for person fields and the company route for company fields, and only the fields and operators that the fields response lists.

Top-level shape

Supported operators

Filters support exact matches, ranges, text and Boolean conditions.

Nested array matching

$elemMatch queries fields inside nested arrays. It is keyed on the field’s nested_path from the fields response, which is not always the outermost array: currentCompanies.company.companyId has nested_path: "currentCompanies", and currentCompanies.positions.title has nested_path: "currentCompanies.positions", so $elemMatch on currentCompanies cannot reference a positions field.
Inside $elemMatch, use the field’s full dotted path. A relative path with a dot, such as company.companyId, returns a 400, although its message suggests a relative path.
In a people search, conditions inside one $elemMatch on currentCompanies, previousCompanies, educations, or a positions path hold on the same entry. On any other path, each condition can match a different entry. Find people currently at a specific company by numeric LinkedIn company ID, which company results expose as source_id:

Excluding results

Use $ne, $nin, $not or $nor to exclude field values. Send exclude_list_ids to omit members of saved lists.

Query examples

Find a company by website domain:
Exclude companies in specific industries:
Exclude records that match any disallowed condition:
Find US-based companies sorted by employee count descending, capped to 8 total results:
Find Canadian companies that have raised any amount and mention technology in categories or keywords:
Search several fields at once with $search:
Find people by current job title:
Fields with a doubly nested path accept $elemMatch on the inner nested path:

DSL filters

Top-level shape

Supported query clauses

Query examples

Range filter:
Multi-field full-text search:
Nested query:
Exclude with must_not:

Try it

Open the Search People API Reference playground.
For the original routes, see Legacy Filter Search.