Best LinkedIn scrapers on Apify 2026
The three best LinkedIn scrapers on Apify for 2026 are: Mass LinkedIn Profile Scraper at $10 per 1,000 public profiles (no cookies), best for prospect lists you already have URLs for; HarvestAPI LinkedIn Company Scraper from $3 per 1,000 companies on Business and up ($3.50 on Scale, $4 on Free and Starter), best for firmographics and TAM sizing; and Bebity LinkedIn Jobs Scraper at $29.99/month for hiring-intel volume today, switching to pay-per-event pricing on 15 September 2026 — ahead of Apify's platform-wide 1 October 2026 rental retirement, not on it. Four are vendor-attested cookie-free; the fifth exposes no cookie input in its schema. None asks for your LinkedIn session cookie.
LinkedIn is the richest public B2B graph online, and the most aggressively defended against automation of any major site. On the Apify Store, maintained Actors handle pagination, login walls, retries, and field mapping so you can export JSON/CSV instead of hand-copying. The tradeoff is real: Actors that need session cookies carry account-ban risk, cookieless ones trade depth for safety. If LinkedIn fingerprinting is a concern, also see our guide to the best proxies for LinkedIn scraping in 2026. This page focuses on LinkedIn alone; for picks across Google Maps, Instagram, TikTok, and other categories, see the full best Apify Actors roundup.
Store metrics and prices drift, so confirm on the Actor page before running volume. Prices below were re-verified on 2026-09-09 directly against each Actor's own pricing record at api.apify.com (previously checked 2026-05-26; links cite the canonical Store URLs). What changed since May: the HarvestAPI Company Scraper's price is now shown per subscription tier instead of one flat figure; its Profile Search's email-lookup charge is confirmed to replace the base per-profile charge rather than stack on top of it; and the Bebity Jobs Scraper's pay-per-event cutover date is corrected from 1 October to 15 September 2026.
LinkedIn is the most expensive of the Apify scrapers we have tested at $10 per 1,000 profiles on the Free plan; Google Maps and Reddit cost $4 for the same volume, so budget accordingly if LinkedIn is one input among several.
Major LinkedIn Actor types (comparison)
| Actor type | Primary output | Typical use | Store examples |
|---|---|---|---|
| Profile / people | Name, headline, experience, skills, education, sometimes email/phone | B2B prospecting, recruiting shortlists | Mass LinkedIn Profile Scraper |
| Company | Industry, size, specialties, HQ, employee bands | Account research, TAM sizing | LinkedIn Company Scraper |
| Jobs | Title, location, description, company, seniority signals | Hiring trends, competitive TA intel | LinkedIn Jobs Scraper |
| Search → profiles | Profiles matching title/geo/industry filters | List building without manual scrolling | LinkedIn Profile Search |
| Posts / content | Post text, engagement metrics (where exposed) | Brand monitoring, thought-leadership tracking | Posts Search Scraper (no cookies) |
| Messaging / inbox (rare) | Highly restricted; often cookie-heavy | High risk. Most teams should avoid | Not recommended; review ToS |
Pricing & posture snapshot
| Actor | Model | Cost | Cookies? | Notes |
|---|---|---|---|---|
| Mass LinkedIn Profile Scraper | Pay-per-event | $10 / 1,000 profiles | No | Public profile fields + optional email/mobile enrichment (mobile is paid-plan only). |
| LinkedIn Profile Search | Pay-per-event | $0.10/search page; $0.004/full profile — or $0.01/full profile with email lookup, which replaces the $0.004 rather than adding to it | No | Feed a LinkedIn search URL. "Short" mode = 25 thin profiles/page; "Full" opens each profile. Per-event prices fall on higher plans: a search page is $0.10 on Free and Starter, $0.08 on Scale, $0.05 on Business and up. |
| LinkedIn Company Scraper (HarvestAPI) | Pay-per-event | $3 / 1,000 companies on Business and up (Gold tier), $3.50 / 1,000 on Scale (Silver), $4 / 1,000 on Free and Starter (Bronze) | No | Firmographics, HQ, headcount bands, specialties, founding year, follower count. Replaces older rental-priced options. |
| LinkedIn Jobs Scraper | Monthly rental until 15 Sep 2026, pay-per-event after (see note) | $29.99/mo now; after 15 Sep, per 1,000 jobs: $1.50 Free, $1.25 Starter, $1.10 Scale, $1.00 Business and up | No cookie input exposed (not vendor-attested) | Job posts with full descriptions, location, seniority. |
| LinkedIn Posts Search Scraper | Pay-per-event | $5 / 1,000 posts | No | Keyword/hashtag search → post text + engagement where exposed. |
Apify blocked new rental Actors on 1 April 2026 and retires the rental model platform-wide on 1 October 2026. Bebity's own cutover is earlier: on 15 September 2026 the $29.99/mo plan above is replaced by pay-per-event pricing — launch rates of $0.0015 per job result on the Free plan, $0.00125 on Starter (Bronze tier), $0.0011 on Scale (Silver), and $0.001 per job (about $1 per 1,000) on Business (Gold) and above, plus small optional charges if you turn on company or hiring-contact enrichment. Bebity's own change note on the pricing record calls these "introductory launch prices... likely to come down," so check the Actor's Pricing tab before committing a recurring jobs pipeline to it. Everything else on this page is already pay-per-event and unaffected. (Verified against Bebity's live pricing record at api.apify.com, 2026-09-09.)
Rule of thumb: pay-per-event/result scales linearly and is predictable at any volume. A flat monthly rental only wins at sustained high daily volume, and once Bebity's Jobs Scraper — the last rental Actor on this page — switches over on 15 September 2026, that trade-off disappears here entirely. See the Apify pricing breakdown for plan-level compute-unit costs that stack on top of Actor fees. Walkthrough in the LinkedIn scraper tutorial and no-code profile guide.
Picking the right Actor: profile vs company vs post vs search
Four inputs, four different Actors. Don't mix them up.
- Profile Actors (
dev_fusion/linkedin-profile-scraper): input is a list of public/in/usernameURLs. Output: headline, experience array, skills, education, sometimes email. Best when you already have the URLs (CSV import, CRM export). - Profile Search (
harvestapi/linkedin-profile-search): input is a LinkedIn search URL with filters (title, geo, industry, current company). Output: paginated profile list. Best when you're building a list from scratch, but cost scales per page of 25, so narrow your filter before running. - Company Actors (
harvestapi/linkedin-company): input is a list of/company/slugURLs. Output: firmographics, employee bands, specialties. Do not expect full employee rosters. That's a different, far higher-risk surface. - Post Actors (
apimaestro/linkedin-posts-search-scraper-no-cookies): keyword/hashtag input, public post text + engagement where LinkedIn exposes it. Engagement counts are "as-rendered" and can lag.
B2B lead generation
Pipeline: Profile Search → dedupe on LinkedIn URL → enrichment (email/phone) → CRM. At $10/1k profiles, 1,000 targeted leads cost ~$10 in Actor fees before enrichment. See our lead-generation use-case playbook and the broader best lead-generation Actors round-up for complementary tools (email finders, intent signals). Honor CAN-SPAM/GDPR opt-outs and document lawful basis before outbound.
Recruiting & talent mapping
Jobs Actors reveal what competitors are hiring and where. Pair with company Actors for headcount trend context. Treat every profile field as personal data under GDPR/CCPA. Our is web scraping legal? guide covers the jurisdictional basics.
Market & competitor research
Company + Posts together map positioning: firmographics from one, messaging cadence from the other. Posts engagement is directional, not audit-grade. For broader social listening across X, Instagram, TikTok and YouTube, branch to best social media scrapers on Apify.
Field coverage caveats
- Email/phone on profile Actors comes from third-party enrichment, not from LinkedIn directly. Hit rates are 20–60% depending on ICP and region; B2C profiles are near-zero. Mobile numbers on
dev_fusionare gated to paid Apify plans. - Connections / network graph: not exposed by any production-grade no-cookie Actor. If a listing promises it, assume cookies and account risk.
- Messaging / InMail / inbox: avoid. Even one-off automated sends violate LinkedIn's User Agreement cleanly.
Legal, compliance & LinkedIn ToS
LinkedIn’s User Agreement and Professional Community Policies restrict automated access and bulk collection in many cases.
What the case law actually says. The common summary that "courts allowed public profile scraping in hiQ v. LinkedIn" is misleading and stops halfway through the story. At the preliminary-injunction stage the Ninth Circuit held that hiQ's scraping of publicly accessible pages likely did not violate the CFAA. But the case did not end there. In November 2022 the district court held LinkedIn's User Agreement anti-scraping terms enforceable as contract, and on 8 December 2022 the court entered a consent judgment and permanent injunction: a $500,000 judgment against hiQ, an order to cease all LinkedIn scraping, and destruction of the scraped data and derived source code. hiQ won the headline CFAA point and still lost the case.
The pattern repeated in LinkedIn v. Nubela (Proxycurl) (N.D. Cal., filed January 2025, settled mid-2025): Proxycurl shut down and deleted its data.
The practical lesson is narrower and more useful than "scraping public data is legal": both enforcement actions that actually bit turned on fake accounts and authenticated access, not on reading public pages. That is precisely why the cookie-free Actors below sit in a materially safer posture than any tool asking you to paste your own li_at session cookie. Supplying your session cookie means you are the one accepting and then breaching the User Agreement.
A court outcome is not permission for every workflow. This is general information, not legal advice.
Practical guardrails
- Prefer public pages and transparent business purposes; document your lawful basis for processing personal data.
- Do not use scraped data for spam, harassment, or evading blocks.
- Review our is web scraping legal? guide with counsel for high-risk programs.
Apify provides infrastructure; you remain responsible for how you configure Actors and use the data.
Account safety & technical hygiene
Some Actors work without LinkedIn cookies; others require session cookies for deeper surfaces; READMEs spell this out.
| Practice | Reason |
|---|---|
| Secondary (“burner”) accounts for cookie flows | Protects your primary company identity |
| Residential proxies when recommended | Reduces obvious data-center fingerprints |
| Low concurrency + backoff | Mimics human pacing; lowers hard blocks |
| Read Pricing + Input schema tabs | Avoid surprise bills and invalid inputs |
Apify Proxy is available when an Actor’s documentation calls for rotating IPs.
Pull 10–20 records, validate fields, estimate cost from the Pricing tab, then scale. Create a free Apify account to use monthly platform credits.
For most teams: a profile-focused Actor such as Mass LinkedIn Profile Scraper, LinkedIn Company Scraper for accounts, LinkedIn Jobs Scraper for hiring intelligence, and LinkedIn Profile Search when you already have a filtered LinkedIn search URL. Always confirm fields in each Actor’s live README.
Some Actors scrape public profile pages without cookies; others require session cookies for deeper data. Cookie-based flows carry higher enforcement risk; use secondary accounts and follow the Actor documentation.
Yes. LinkedIn actively mitigates automation. Even successful technical runs can violate the User Agreement. Minimize risk with conservative volumes, proxies when advised, and legal review for your jurisdiction.
Certain profile Actors attempt email discovery when data is public or matched via enrichment partners. Results are never guaranteed; respect anti-spam laws and LinkedIn’s messaging rules.
Sales Navigator is LinkedIn’s paid prospecting product with export constraints. Apify Actors offer flexible dataset exports for analytics and ops, but they are not endorsed by LinkedIn and may conflict with LinkedIn’s terms if misused.
Common mistakes and fixes
Empty rows or high failure rate.
Reduce concurrency, widen delays, and confirm inputs (public URLs vs search URLs). Read the Actor log and README for cookie or proxy requirements.
Account warnings after using cookie-based Actors.
Stop using primary accounts; prefer dedicated test accounts, residential proxies where appropriate, and conservative volumes. Scraping may violate LinkedIn’s rules; see compliance below.
Unexpected pricing on the invoice.
Open the Actor **Pricing** tab. Many LinkedIn tools are pay-per-result or event-based. Run a 10-row test before scaling.