Build a filter
- List the fields you can filter on with
GET /v1/people/search/fieldsorGET /v1/companies/search/fields. Field names differ between people and companies. - 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. - 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 fromGET /v1/jobs/{job_id}/items.
Item response
fullName and linkedinUrl. Each item repeats the retained search parameters in input.
Parameters
Exact, range or Boolean conditions, as simple filters or DSL filters.
filters, query, seeds or search_id. See Deep Search for the others.
Maximum results. Minimum 1, up to the
max_results returned by GET /v1/people/search/fields or GET /v1/companies/search/fields.HTTPS callback URL. See Outgoing Webhooks.
Discover fields
ReadGET /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 infields 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
UsePOST /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 astechnologies_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 underfilters. 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.
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:$search:
$elemMatch on the inner nested path:
DSL filters
Top-level shape
Supported query clauses
Query examples
Range filter:must_not:
Try it
Open the Search People API Reference playground.
Related
For the original routes, see Legacy Filter Search.