LinkedIn Profile Scraper - Search People, No Cookie Needed
Pricing
Pay per event
LinkedIn Profile Scraper - Search People, No Cookie Needed
Find people by what they do and get their public LinkedIn profile: name, headline, location, current employer, follower and connection counts, About text and education. Search by phrase or pass profile URLs. No login and no session cookie of your own.
Pricing
Pay per event
Rating
0.0
(0)
Developer
SR
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
3 days ago
Last modified
Categories
Share
LinkedIn Profile Scraper
Find people by what they do, and get their public LinkedIn profile. No login, no session cookie of your own, nothing to paste from your browser.
Type the kind of phrase you would use to describe someone, like
ecommerce manager netherlands, and get back a table of people: name, role,
current employer, location, follower and connection counts, their About text
and their education.
You can also pass profile URLs you already have, as full links or bare slugs, and combine both in one run.
What you get, and the one thing you do not
| Field | Where it comes from |
|---|---|
name, first_name, last_name | The profile |
headline | The search index |
current_company | The profile's own page title |
location, followers, connections | The profile |
about | The profile |
education | The profile |
positions | The profile: company and location |
Job titles per position are not available. LinkedIn ships that field empty
to anonymous visitors, on every position, on every profile tested. So
positions tells you where somebody worked and roughly where they were based,
not what they were called there. Dates are withheld the same way.
The row carries titles_available so you can see this is a property of the
source rather than a gap in the run. If LinkedIn ever changes it, that flag
goes true and the column fills itself.
This is why headline matters. The search index kept the person's role
from when their profile was crawlable, so the index knows the role and the live
page knows the employer. One search returned "Edo Voets - E-Commerce Manager"
while the live page for the same person says "Moët Hennessy Nederland BV".
Neither half is complete on its own, which is why both are on the row.
Searching
People searches takes a phrase per line and looks it up in the public profile index. Search pages per phrase decides how deep, at roughly seven to eleven profiles per page.
Write the phrase the way the person would describe themselves, because that is
what the index matched on. head of procurement retail germany works;
decision maker in supply chain does not, because nobody writes that on their
profile.
Country steers both halves: it picks the index's market and decides where
the profile is read from, and LinkedIn serves the page in that country's
language, so a Dutch profile read through nl comes back with Dutch labels.
Errors
| Code | Meaning |
|---|---|
blocked | The profile could not be read after every attempt |
search_failed | The index could not be searched for that phrase |
no_results | Nothing matched and no URLs were given |
bad_input | Neither a search phrase nor a URL was given |
A profile that was found but not read still appears as a row, with
fetched: falseRaise Attempts per profile if you see blocked. Only profiles that were
actually read are billed.
A note on reliability
Access here is narrow and can change without warning. If a run suddenly returns
blocked across the board where it worked last week, that is what has
happened; it is not your search phrase. Check profilesRead against
profilesFound in the run summary, which is exactly the ratio that tells the
two apart.
Related actors
linkedin-jobs-scraper for job postings, linkedin-ads-library for what a
company is advertising, and the company actors for the organisations these
people work at.