Skip to main content
People search identifies buyers at target accounts or builds a talent pool for a role. Send every people request to POST /search/people.

Which people field names should you use?

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.

What does a people search request look like?

This Ludicrous request finds US profiles whose current title includes both product and manager, with at least 1,000 followers:
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 “Senior Manager, Product” still matches. Punctuation between the words does not prevent a match, word order does not matter and extra words in the title are allowed.

How should you handle missing profile fields?

Location and employer fields can be missing from individual profiles. A missing value is not evidence that the corresponding real-world fact is false. A profile with no current_company_name is a profile that does not publish an employer, not a person who is unemployed. Handle absent or null values without failing the whole record, and avoid filters that silently drop every profile where an optional field is blank.

Which fields does the summary view return?

The summary view returns 11 fields: name, current_title, current_company_name, current_company_industry, location, city, country_code, followers, connections, url and avatar. A field the profile has no value for is left out rather than returned as null. Request a fields list when your application needs a specific set. See Business Search field views.