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 access-gated retrieval 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.

More scrapers from our toolkit

Building a data pipeline? These actors pair well with this one — each runs on your own Apify account with the same pay-per-result pricing, no subscription:

• PagesJaunes Directory Scraper
• Skip Trace People Finder
• Trustpilot Reviews Scraper
• Upwork Talent Scraper
• Website Contact Extractor
• Yellowpages Scraper

Chain any of them together from the Integrations tab (the Run succeeded trigger) to build a multi-step workflow — one actor's output feeds the next.

Rate this Actor

If LinkedIn Profile Scraper saved you time, please rate it on the Apify Store. A rating takes a few seconds and helps other people find a working scraper. If something did not work, open an issue on the Actor page and we will fix it.

Usage statistics

This Actor creates a small, content-free summary at the end of each run. It is used only to monitor reliability and improve this Actor. A copy is saved as USAGE_STATS in your own Apify key-value store, so you can see the exact record created for your run.

Set disableUsageStats to true in the input to opt out. Nothing is sent then; your USAGE_STATS record only says that statistics were disabled.

Only these fields are recorded:

• schema version, Actor name and build number;
• UTC start and finish hour (not a precise timestamp);
• run duration, number of results and time to the first result, each as a coarse range;
• whether the result was empty, the end status, and an error type from a fixed list;
• memory setting and counts of charged events;
• names of the input fields you set, never their values;
• the selected option for input fields that offer a fixed list of choices (for example a sort order).

We do not collect input text, search terms, URLs, domains, usernames, email addresses, names, proxy credentials, tokens, scraped records, output items, raw error messages, stack traces, or hashes of any of those values. Records are kept for no longer than 13 months, used only as aggregated operational statistics, and never sold or shared.

Additional fields (Phase 2)

This Actor also records your Apify user ID, whether Apify marks the account as paying, the size range of list inputs, the selected country when the input offers a fixed list of countries, and one category from a fixed Actor taxonomy. We use these fields only for aggregate reliability, repeat-use and cross-Actor analysis; reports suppress any cell with fewer than five distinct users.

The same disableUsageStats: true input flag turns these fields off too. The user ID is removed after 13 months; we do not export, sell, share, or attempt to re-identify this data.

Run-outcome signals (v2)

To learn whether a run did what it was asked to do, the record also holds a few more coarse ranges and yes/no flags. None of them contains content:

• the result limit you asked for (a range, when the input has one) and what share of it was delivered;
• results delivered per input item you listed (a range);
• output quality as ranges: how fully the result fields were filled, the share of rows that look like errors, the share of duplicate rows, and how many different fields appeared. These are counted in memory while results are saved; no result content is kept;
• how the run was started (console, API, schedule, webhook, another Actor);
• how it ended: stopped by you, timed out, reached the requested limit, stopped by the charge limit, and how many times the platform moved the run;
• if this Actor reports it: how many items to process worked or failed (ranges) and one failure reason from a fixed list;
• a short code made from the names of the input fields you set, never their values.

Repeat-run fingerprint (v2)

When your Apify user ID is recorded (see above), the record also holds an 8-character one-way code made from your input (proxy settings left out) and this Actor's name. It only lets us see that the same account ran the same input again soon after an unsatisfying run; we never see the input itself. It is stored only in the database, never published, and reports use it in aggregate with the same five-user minimum. It is the one exception to the statement above that no hashes are collected, and disableUsageStats: true turns it off.