Search LinkedIn people by keyword with job-title, location, company, school, seniority and other filters; each hit is a full profile.
5 credits/ result
RestrictedAt least 130 credits a call.
You only pay when data comes back.
curl -X POST "https://api.primaryapi.com/v1/run/linkedin.search_profiles" \
-H "Authorization: Bearer $PRIMARYAPI_API_KEY" \
-H "Content-Type: application/json" \
-d '{"query":"head of data","jobTitle":"CTO","location":"United States","limit":10}'{
"output": {
"found": true,
"data": {
"nextCursor": "<string | null>",
"items": [
{
"handle": "<string | null>",
"name": "<string | null>",
"followerCount": "<integer | null>",
"openToWork": "<boolean | null>", …
}
]
}
},
"credits": 130
}Input and output
29 fields
head of data.CTO.United States.10.33 fields
Good to know
Needs approval. This API returns personal data. Your account needs approval, and you accept the permissible-purpose terms, before a key can call it. Calls made before that are refused and never charged. Restricted: needs an approved account and an accepted permissible purpose. Public LinkedIn data only. LinkedIn’s User Agreement restricts automated collection and LinkedIn enforces it; use the data for lawful purposes, keep copies only as long as you need them, and treat post and article text as the author’s content (analysis, not republication). Results contain personal data about identifiable people (GDPR, UK GDPR, CCPA): have a lawful basis, honour deletion requests, and never use it for spam or unsolicited bulk outreach. Bulk people search is the highest-risk LinkedIn use: keep to the purpose you declared. Request access →
One call reads one search page (up to 25 people). Serves the first page only.
People search depends on what LinkedIn shows for the query. Some results can be partial.
The per-call fee is charged even when the search finds nobody.
One page per call. Send nextCursor back as cursor to read the next page.
The same key and credits work for every API.