Skip to main content
This page shows the shape query takes in each mode, the fields a people search can filter on with the operator each accepts and what a request looks like. People requests go to POST /search/people. For companies, see Company search.

Writing queries

The shape of query follows the search mode:
  • Ludicrous takes a JSON object of conditions on the searchable fields, combined with and, or and not. Operators and value shapes are in Business Search query syntax.
  • Instant and Smart take a plain-language sentence of up to 200 characters. Business Search turns the sentence into one structured query on the same fields. A sentence that asks for a job title is ranked on the title, role and about text together. A sentence that reads like a recruiting brief, with a role, an industry and a skill, is scored on the role, company and skill field groups independently.

Searchable fields

The operator a field accepts depends on the field’s type. Text fields accept only the text operator. Typed fields, such as strings and integers, accept equals, in and range. Sending equals to a text field returns HTTP 400.
Location and employer fields can be missing from individual profiles, and a missing value is not evidence that the fact is false: a profile with no current_company_name publishes no employer. Handle absent or null values without failing the whole record, and avoid filters that silently drop every profile where an optional field is blank.
A people search filters only on the fields in this table. Company attributes such as funding and headquarters are filters of company search, so one request cannot find people by them. To find people at companies that match company filters, run a company search first, then a people search. See How to run a multi-step search.

Example request

A Ludicrous request finds US profiles whose current title includes both cloud and engineer and whose certifications mention AWS, and names five output fields:Sample request
Sample responseThe first of the three returned records:
mode: "all" inside the text condition requires every search word to match. The words do not need to form an exact phrase, so a title of “Cloud DevOps Engineer” still matches. Punctuation between the words does not prevent a match, word order does not matter and extra words in the title are allowed.
For the fields each view returns and how view relates to query, see Business Search field views. For more tested requests, see Business Search query examples.