How to Scrape LinkedIn Data Legally in 2026

By Marcus Reiner · 2026-02-19 · 10 min read · Legal

Post-hiQ Labs v. LinkedIn, scraping public profiles is generally legal in the US — but the technical and contract layers still matter.

What hiQ v. LinkedIn established

The 9th Circuit (and SCOTUS's denial of cert) effectively held that scraping publicly accessible LinkedIn data does not violate the CFAA. But: (1) it's a US ruling, (2) LinkedIn can still pursue breach-of-contract via the User Agreement if you logged in, and (3) GDPR/CCPA personal-data rules apply regardless of access method.

Legal vs not-legal in plain English

Likely OK: pulling public profile fields (name, headline, employer, public posts) without an authenticated session, for non-marketing purposes, with appropriate data-minimization.

Risky: scraping while logged in (you accepted the User Agreement), pulling email/phone, training a public ML model on scraped profiles, reselling the data.

Technical stack — public-page only

LinkedIn aggressively blocks scrapers. Use Bright Data's LinkedIn dataset (pre-collected, refreshed weekly) for compliance + scale, or Oxylabs LinkedIn-focused scraper API for ad-hoc.

• Bright Data LinkedIn Dataset — 800M+ profiles, GDPR-compliant sourcing
• Oxylabs LinkedIn Scraper API — pay per result
• Decodo residential + headless Chrome — DIY route, expect 60-70% success

GDPR is the real constraint for EU data

If any subject is in the EU/UK, you need a lawful basis (legitimate interest works for B2B contact data with proper LIA), a privacy notice mechanism, and DSR fulfillment. This is more work than the scraping itself.

Do not log in

Authenticated scraping is a CFAA + ToS breach in nearly every jurisdiction. If your use case requires logged-in data, partner via the official LinkedIn Sales Navigator API or Talent Solutions API.

Frequently Asked Questions