LinkedIn People Search API — Filter by Title & Seniority
This is the widest filter set in the catalog. Search people by free-text query, current or past company, current or past job title, seniority, function, industry, location, years of experience, years at the current company, company headcount, and first or last name.
{
"session_id": "b7c1…",
"kind": "linkedin_people_search",
"searchQuery": "head of revenue operations",
"human": "Found 3 matching people…",
"machine": {
"total_items": 3,
"first_item": {
"firstName": "Jane",
"lastName": "Doe",
"profileUrl": "https://www.linkedin.com/in/example",
"headline": "Head of Revenue Operations",
"currentCompany": "Acme Technologies",
"location": "Austin, Texas"
}
},
"points_per_25_results": 100,
"points_per_profile": 5,
"total_points": 115
}- You send
- A search query with title, seniority, company and location filters
- You get back
- Matching people with profile URLs, headlines and companies
- Coverage
- People with a public profile, worldwide.
- Price
- 100 points per 25 results, plus 5 per profile — $0.10 per block of 25
- Charged per block of 25 results plus a per-profile charge. A search that matches nothing is not billed.
Ways to get this data
Three approaches teams use today, and where each one runs into trouble.
| Approach | What it takes | Cost | Trade-off |
|---|---|---|---|
| Searching and copying by hand | Filter, scroll, copy, repeat | Free, and hours per list | Nobody keeps a list current this way |
| A sales-intelligence seat | A per-seat contract with export limits | Per seat, annually | Export caps are the whole business model, so the data resists leaving the tool |
| NeuralVerge | One request, filters as parameters | Per block of 25 plus per profile | A loose query gets expensive quickly — the filters are there to be used |
What you get back
Every field in the response shown above.
| Field | Type | Description |
|---|---|---|
total_items | number | How many people came back. |
firstName | string | First name. |
lastName | string | Last name. |
profileUrl | string | Profile URL. |
headline | string | The person's headline. |
currentCompany | string | Where they work now. |
location | string | Where they are based. |
How to run it
The same lookup works from the app, the API, or as a tool an agent can call mid-task.
Every parameter is optional, which makes it easy to run an accidentally enormous query. Set maxResults and at least one narrowing filter before you run it for the first time.
curl -X POST https://api.neuralverge.ai/functions/v1/run-linkedin-people-search \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"searchQuery": "head of revenue operations",
"currentJobTitleFilter": ["Head of Revenue Operations"],
"seniorityLevelFilter": ["Director"],
"locations": ["United States"],
"maxResults": 25
}'What teams use it for
Where this field shows up in an actual workflow.
Find the people holding a specific role across a defined set of companies.
Filter by function, seniority and years of experience to build a shortlist.
Find everyone in the relevant function at an account, not just your one contact.
Re-run a saved filter to catch the people who have changed roles.
Coverage, freshness and limits
What this source covers, how fresh it is, and where it stops.
People with a public profile, worldwide.
Searched at request time.
This source returns personal data. Use it for legitimate business purposes under your own lawful basis, honour deletion and opt-out requests, and check the acceptable use policy for what is out of bounds.
- —Filter vocabularies are the platform's own — a seniority or function label may not map onto your internal one.
- —A search with no filters and no result cap is the fastest way to spend points badly.
- —Results reflect what people publish about themselves, including titles they gave themselves.
Questions, answered
100 points per block of 25 results, plus 5 points per profile returned. The response carries both rates and the total, so you can reconcile any run precisely.
Related sources
Try linkedin people search on your own data
One request format across every source in the catalog.