Use LinkedIn People Search by Name with Company & School Filters with Python
Search LinkedIn for a list of names and get matching profiles with headline, location, current role and company, connection degree, and profile picture.
1. Choose the data you need
Review the published README for supported collection modes, examples, and limits. The recipe below uses the current published input definition.
2. Prepare a source-based input
This JSON contains published prefills and required-field defaults. Review every value for your task before running it; it is not a promise of successful collection.
{
"enrichProfiles": true,
"includeHeadlinesFromSearchEngines": false,
"maxResultsPerName": 1,
"names": [
"Satya Nadella"
]
}
Download input.example.json and save your reviewed copy as input.json.
| Field | Type | Required | Description |
|---|---|---|---|
names | array | required | Person names to look up. Use a full name ("Satya Nadella"), a single name, or "First Middle Last". Prefix a single term with "first:" or "last:" for a one-sided search. |
maxResultsPerName | integer | optional | Maximum profiles to return for each name. LinkedIn's public directory lists up to 50 candidates per name. |
currentCompany | string | optional | Keep only people whose current employer contains this text, e.g. "Microsoft" or "Conrad Labs". Checked against the profile the actor opens for each candidate. |
location | string | optional | Keep only people whose location contains this text, e.g. "London" or "Pakistan". |
enrichProfiles | boolean | optional | Open each matched profile's public page to fill photo, about, followers, education and a verified current employer. Turn off for a faster, directory-only result. |
includeHeadlinesFromSearchEngines | boolean | optional | When the directory has fewer matches than requested, also check public search-engine results for the name. Also recovers indexed headlines. Free and best-effort. |
3. Start an Actor run
Set APIFY_TOKEN in your environment. Python 3.10 or newer is sufficient; this recipe uses no third-party packages.
Execution may incur charges. Review current pricing on Apify. The request asks for a 120-second timeout and a charge limit; these settings are subject to Apify’s pricing and do not guarantee an all-inclusive spending cap.
import json
import os
import urllib.request
# Save the schema-derived example as input.json; review and edit it first.
with open("input.json", encoding="utf-8") as stream:
actor_input = json.load(stream)
token = os.environ["APIFY_TOKEN"]
request = urllib.request.Request(
"https://api.apify.com/v2/acts/qbDkwl2DwUF7XO3zX/runs?timeout=120&maxTotalChargeUsd=0.50",
data=json.dumps(actor_input).encode("utf-8"),
headers={"Authorization": "Bearer " + token, "Content-Type": "application/json"},
method="POST",
)
# This starts a potentially billable run. Do not automatically retry this POST.
with urllib.request.urlopen(request, timeout=40) as response:
run = json.load(response)["data"]
print("Run ID:", run["id"])
print("Status:", run["status"])
# Inspect and download results in Apify Console once the run succeeds.
4. Inspect the actual results
Open the run in Apify Console and wait for a successful completion. Use the published output schema to locate results and the dataset schema to understand declared views. Missing or optional record fields must not be treated as guaranteed values.
Matched LinkedIn profiles with name, profile URL, current employer, headline, location, photo, followers, about and education when publicly available.
Questions before you run
Which inputs are required?
The published required fields are names
What does this guide verify?
The fields, prefills, and schema links are rendered from the published build. This is a usage recipe, not a paid live extraction test. Source availability and collection results can vary.
What if the run request times out?
Check Apify Console before retrying. The first request may already have created a run. Do not automatically repeat a run-creation POST.
Generated from source build 7KkQyVManVFJioeS8 and its README and schemas. Source changes regenerate this guide; no third-party editorial claims are inferred.