Search
Faceted discovery across people, companies, groups, and posts.
One search surface, four facets. Every result carries the same provenance stamp as the underlying record — so a search is an ICP query, not a scrape. Search is flat per request: a query that returns 50 hits costs the same as one that returns 5.
- GET5 credits
/v1/search/peopleSearch People
People search over LinkedIn (migration pending).
- GET2 credits
/v1/search/companiesSearch Companies
Company search (migration pending).
- GET2 credits
/v1/search/groupsSearch Groups
Group search (migration pending).
- GET2 credits
/v1/search/postsSearch Posts
Content/posts search (migration pending).
Search people
/v1/search/people5 creditsStub — returns 501. Will wrap the voyager `Search — People` dash-clusters endpoint with the SearchClusterCollection-210 decoration.
Keyword + filters across LinkedIn's people graph. The response shape
mirrors a stripped-down /v1/profiles record —
enough for triage; call profiles for the full résumé.
For tighter ICP filters (current company, school, geography), pass
the canonical IDs from
/v1/companies/by-id and
/v1/locations.
Search companies
/v1/search/companies2 creditsStub — returns 501. Same dash-clusters endpoint with `resultType=COMPANIES`.
Filter by industry, headcount band, HQ region. Ideal for ICP
company-list building — combine with
/v1/companies/:slug/employees to expand each
hit into named people.
Search groups
/v1/search/groups2 creditsStub — returns 501. Same dash-clusters endpoint with `resultType=GROUPS`.
Find LinkedIn groups by keyword and topic — a niche-community
discovery primitive. Pair with
/v1/groups/:id/members to enumerate.
Search posts
/v1/search/posts2 creditsStub — returns 501. Wraps the voyager `Search — Posts` graphql endpoint (different from dash-clusters REST).
Find posts by keyword. Useful for thought-leadership monitoring,
launch-tracking, and topic timelines. Each hit is an activity ID —
feed it into /v1/posts/:id for the full record.
Notes
- People search caps at LinkedIn's ~1,000-result ceiling, regardless
of your
limit/offset. Use tighter filters to surface different pages rather than trying to paginate past it. - Search results cache for 15 minutes per (filters, page) tuple to protect against pathological agent loops.
- Empty result sets are never charged.