Introduction
The People Search endpoint returns paginated person profiles matching a combination of filters. All filters are optional and combined with AND logic. Results are drawn from our cache-based search index. This endpoint never triggers a live fetch.
Use this endpoint to discover profiles that match criteria like job title, company, industry, or location, then chain into Profile for the complete data of any hit.
Authorization
apikey
string
required
Authorization: Bearer YOUR_API_KEY header.Request body
All filters are optional and combined with AND logic. Scalar filters live in the table below; the three nested-object filters (followersCount, currentCompanyEmployeeCountRange, location) are documented as expandable field items right after.
firstName
string
lastName
string
headline
string
isOpenToWork
boolean
isPremium
boolean
isVerified
boolean
currentPositionTitle
string | string[]
excludeCurrentPositionTitle
string | string[]
currentCompanyName
string
currentCompanyLinkedinId
string
currentCompanyPublicId
string
currentCompanyId
string
com_...) of the current employer. Single value only. Strictly matches people currently working at the company. This id comes from the currentCompanyId field in person search results, or the id field returned by company enrichment endpoints.currentCompanyIndustry
string | string[]
maxDataAgeDate
string
page
number
1)perPage
number
100)Note: Title matching is token-based, not exact:
"CTO"also matches"Deputy CTO". Multiple titles are OR-matched, and exclusions always win over matches.
Response structure
Note: This endpoint uses a nested envelope. The top-level V2
datafield wraps an inner search payload that contains the actual results array (data.data) and the pagination info (data.metadata). See the example response for the exact shape.
success
boolean
true if the request was processed successfullyerror
null
null on success