LinkedIn Profile Scraper — No API Key, No Cookies

Turn a list of LinkedIn profile URLs (or bare slugs) into clean, structured records — with no login, no cookies, no li_at, and no API key. Paste the URLs, press Run, get a tidy table back. Nothing to configure, nothing to expire.

What you'd use it for

• Clay / Make / n8n enrichment — drop this into an enrichment column or an automation step to hydrate a list of LinkedIn URLs into name, headline, current company, and location. The output is a flat, predictable schema that maps straight onto your CRM or spreadsheet.
• Recruiter & sales sourcing — you already have the profile links (from a search export, a scraped SERP, a conference list). This turns them into a workable contact sheet: who they are, where they work, where they studied.
• List cleaning / dedup — verify a profile still resolves and pull its canonical URL + slug so your list stays current.

Why this one

Most LinkedIn scrapers demand your session cookie (li_at) or a paid API key — which expires constantly, risks your account, and breaks mid-run. This actor reads only the public data LinkedIn already serves to social-link-preview bots (the same SEO/JSON-LD surface that powers a link unfurl in Slack or X). There is no account to ban and nothing for you to supply.

It also ships something rivals hide: a parse_confidence score and a parse_path on every record, so you can see exactly how complete each profile is and which extraction path produced it — instead of guessing whether a blank field means "no data" or "scraper broke".

Output fields

Field	Description
name, first_name, last_name	Full name + split parts
headline	Profile tagline / role summary
job_title	Current job title(s)
current_company, current_company_url	Current employer + its LinkedIn page
location, country	Region (free-text) + country code
education	List of schools {name, url, start, end}
experience	List of companies {name, url, start, end} (from public JSON-LD)
photo_url	Profile photo (LinkedIn CDN; time-limited — fetch promptly)
follower_count	Followers, when LinkedIn exposes it (partial coverage)
description	About / summary text, when present
same_as	Linked socials (e.g. Twitter/GitHub) + canonical URL
recent_posts	Recent post stubs {headline, url, published} (partial coverage)
profile_url, slug	Canonical URL + vanity slug
parse_path	Which source + UA produced the record (e.g. jsonld:facebookexternalhit/1.1)
parse_confidence	1.0 = full JSON-LD · ~0.6 = OG-meta only · lower = partial
warnings	Machine-readable quality codes (e.g. no_work_history, og_only)

Honest about the anonymous data tier

This scraper reads public, no-cookies data only. That is deliberate — it is what keeps it reliable and account-safe. Some fields are simply not rendered to anonymous visitors, and we return them as null rather than fabricating them:

• Work history is partial. LinkedIn's public JSON-LD exposes current/past company stubs (name + start year), not the full dated role-by-role history. A profile with no public work history gets current_company / experience = null and a no_work_history warning — never a made-up employer.
• Not available anonymously (always null): full dated work history, skills, certifications, recommendations, and contact email/phone. Those need a logged-in session, which we intentionally do not use.
• ~30–40% of profiles have no JSON-LD. For those we fall back to Open Graph meta (name, headline, photo) and mark the record parse_path: og:* with a medium parse_confidence. You always know which tier you got.

Reliability

Requests use social-preview headers and run through Apify Datacenter proxy by default (cheap — LinkedIn allowlists this preview surface), auto-escalating to Residential if datacenter IPs get blocked. Polite per-IP pacing keeps runs clean. Proxy usage is billed to your Apify account; there is no external proxy or proxy key to bring.

Pricing

Pay-per-result: you are charged once per profile record returned. Runs that return nothing for a URL (private/blocked) are not charged for that URL.

Compliance

This actor collects only publicly available information that LinkedIn serves to anonymous social-preview bots — no login, no circumvention of an authentication wall. Scraping public data is broadly lawful (see hiQ v. LinkedIn), but you are the data controller for whatever you collect: use it for legitimate B2B purposes, honor GDPR/CCPA and individuals' rights, and do not use it for spam or any purpose prohibited by applicable law or LinkedIn's terms.