LinkedIn Profile Scraper — work history and education, no login

This Actor collects public LinkedIn profiles by slug or /in/ URL. It returns the headline, about text, dated work history and education, location, exact follower count and languages.

No LinkedIn account, login or cookies are used — this reads what a logged-out visitor sees on the public profile.

What it returns

Field	Type	Notes
fullName	string
headline	string	The short line under the name
about	string	The About section
jobTitles	string[]	Every title held, e.g. ["Co-chair", "Founder"]
location, country	string
currentCompany	string	Most recent employer
positions	object[]	{ company, url, startYear, endYear } — dated work history
education	object[]	{ school, url, startYear, endYear }
followerCount	number	Exact, e.g. 40560540
languages	string[]
imageUrl	string	Profile photo
handle, sourceUrl, collectedAt	string	Provenance for every row

Input

{ "profiles": ["williamhgates", "https://www.linkedin.com/in/satyanadella"] }

Field	Description
profiles	Public profile slugs or /in/ URLs. Required, 1–500.
maxItems	Cap on dataset items. Default 1000. Free plans stop at 250 requests and 250 results — see below.
concurrency	Profiles fetched in parallel. Default 5.

Slugs and full URLs for the same person collapse to one fetch, so a mixed list is never billed twice.

How it reads a profile without logging in

LinkedIn publishes each public profile as schema.org JSON-LD in the page itself, and this Actor reads that structured data directly rather than handing rendered markup to a model. That is what makes the work history dated and the follower count exact: positions and education carry startYear and endYear per entry, and followerCount arrives as 40560540 rather than "40M".

Because the JSON-LD is part of the logged-out page, no LinkedIn account, session cookie or li_at token is involved at any point.

Use cases

• Enriching CRM records with role, employer and tenure
• Recruiting research — who worked where, and for how long
• Mapping an account's org structure before outbound
• Tracking executive moves across a watchlist
• Building alumni or cohort lists from education history

Reliability

Measured across 30 profile slugs in one run: every profile that exists was collected — 19/19, with the other 11 being slugs that do not resolve on LinkedIn and are reported as failures rather than emitted as empty rows.

Fields come from the profile's own structured data, so a value is either present and correct or absent — it does not change between runs for the same profile.

Frequently asked questions

How do I scrape LinkedIn profiles without logging in? Put the public profile slugs or /in/ URLs in the profiles input and run this Actor. It reads the schema.org JSON-LD that LinkedIn publishes on the logged-out public profile, so no LinkedIn account, cookie or session token is required.

Do I need a LinkedIn account, cookies or a session? No. Only the public, logged-out profile is read, and no credentials of any kind are supplied.

Does it return email addresses or phone numbers? No. Contact details are not on the public LinkedIn profile and are deliberately out of scope for this Actor.

Does it include work history with dates? Yes. positions carries company, URL, startYear and endYear per role, and education does the same for schools.

Is the follower count exact or rounded? Exact — followerCount comes back as 40560540 rather than "40M".

How many profiles can one run collect? Up to 500 per run, which is the ceiling on the profiles input, and this Actor returns one row per profile.

What happens with a profile that does not exist? It is recorded under failures in the run's SUMMARY and the rest of the batch still returns. A run in which every profile failed exits with an error.

Can I search LinkedIn for profiles? No. You supply the profiles — the LinkedIn Profile Scraper does not do discovery or keyword search.

Limitations

Public profile fields only: no contact details, no connections, no posts or activity, no skills or endorsements, and no search. Profiles set to fully private return nothing to read and are reported as failures. Only linkedin.com URLs are accepted.

Free plan limit

Runs started from an Apify free plan stop at 250 requests and 250 results, and the run reports that it reached the limit. Any paid plan runs the full input and maxItems you set.

The limit exists because this Actor fetches through our own infrastructure, which Apify does not cover for free-plan runs. It binds on requests as well as results so that a large input list cannot spend those fetches for rows the run will not return.