TL;DR
LinkedIn's official API gives partners narrow, controlled access to specific data — most of the public-facing API endpoints have been removed or restricted to approved enterprise partners. Scraping LinkedIn is explicitly prohibited by the User Agreement and has been the subject of multiple lawsuits, including LinkedIn v. Nubela (Proxycurl) in 2026. So what's left? Three legitimate paths: (1) LinkedIn's sanctioned products (Sales Navigator, Recruiter, official API for approved partners); (2) LinkedIn's own data export for your personal data; (3) browser-based tools like ScrapeMaster that capture data from pages you visit manually. Save policy and ToS pages with Convert: Web to PDF for compliance reference.
What the Official LinkedIn API Actually Provides
LinkedIn's developer platform has shifted dramatically over the years. As of 2026, the public LinkedIn API is heavily restricted:
Sign In with LinkedIn (OAuth). Lets users authenticate with LinkedIn into your application. You get basic profile information from authenticated users, with explicit user permission.
Share on LinkedIn. Lets users share content from your application to LinkedIn.
Marketing Developer Platform (MDP). For approved marketing partners: campaign management, audience targeting, advertising analytics. Requires a partner application and approval.
Talent Solutions API. For approved recruiting partners: integration with LinkedIn Recruiter products. Requires partnership approval.
Sales Solutions API. For approved sales partners: integration with Sales Navigator. Requires partnership approval.
Compliance API. For specific regulatory archiving needs (e.g., financial services). Approval required.
What's NOT available in the public API:
- Bulk profile data download
- Search across LinkedIn members
- Connection graphs of other users
- Posts and content from non-authenticated users
- Company employee lists
The narrow, partner-controlled scope is intentional. LinkedIn limits API access precisely to prevent the bulk data flow that scraping enables.
What LinkedIn's Terms Explicitly Prohibit
LinkedIn's User Agreement lists prohibited activities in its "Don'ts" section. The relevant clauses (paraphrased):
- Develop, support, or use software, devices, scripts, robots, or any other means to scrape the services or copy profiles and other data
- Bypass or circumvent measures used to prevent or restrict access
- Use bots or other automated methods to access the services
- Rent, lease, loan, trade, sell, or otherwise monetize the services or related data without LinkedIn's consent
This wording is direct: "scrape" appears as a named prohibited activity, "bots" appears as a named prohibited tool, and commercial monetization of LinkedIn data without consent is separately prohibited.
For the deeper exact-wording analysis, see our LinkedIn User Agreement scraping breakdown.
Why "Just Use the API" Isn't a Real Answer
When you ask "is scraping LinkedIn ok?", a common response is "use the API instead." In practice, this advice fails for most use cases because the API doesn't provide what people typically want:
| What people want | API supports? | Reality |
|---|---|---|
| Search LinkedIn by job title and company | No | Sales Navigator (paid) only |
| Pull profiles of all employees at a company | No | Sales Navigator (paid) at limited scale |
| Bulk download of contact info | No | Restricted to authenticated user's own |
| Job posting database | Limited | Talent Solutions API (partner-only) |
| Salary and compensation data | No | Not available via API |
| Company news / posts feed | Limited | Restricted to authenticated user's network |
| Recruiter outreach automation | Limited | Recruiter (paid) only |
The narrow API forces most users into one of three options: (1) pay for LinkedIn's premium products like Sales Navigator and Recruiter, (2) attempt unauthorized scraping (the path LinkedIn sues over), or (3) browser-based manual collection.
LinkedIn's Sanctioned Products: What They Cost and Allow
For commercial users with budget, LinkedIn's paid products are the unambiguous safe path:
LinkedIn Sales Navigator
- Search across LinkedIn member base by industry, company, role, etc.
- Save lead lists
- Get notifications about leads (job changes, posts)
- Limited InMail messages
- CRM integrations
- Pricing: ~$100-160/user/month
What it allows: Identifying leads, tracking changes, individual InMail outreach, exporting limited data within Sales Navigator's permitted use.
What it doesn't allow: Bulk export of profile data outside the platform, scraping the underlying data.
LinkedIn Recruiter
- Full LinkedIn member search
- Project pipelines
- Candidate engagement tools
- Bulk InMail
- Job posting integration
- Pricing: significantly higher (depends on contract)
LinkedIn Marketing API (MDP)
For ads platforms and marketing tools. Approved partners only.
LinkedIn Talent and Sales API
For ATS, CRM, and similar platform integrations. Approved partners only.
These are the sanctioned ways to do at-scale work. They're priced for businesses, not individual users.
What the LinkedIn v. Nubela (Proxycurl) Lawsuit Tells Us
The 2026 LinkedIn lawsuit against Nubela (which operates Proxycurl) targets exactly the activity we've described — building a paid commercial API on top of scraped LinkedIn data, then selling access to other companies.
Key takeaways:
LinkedIn pursues commercial scrapers most aggressively. The lawsuit isn't about hobbyists; it's about businesses that profit from LinkedIn data resale.
Multiple legal theories. LinkedIn typically combines breach of contract (User Agreement), CFAA claims, copyright (compilation of profile data), and anti-circumvention claims (DMCA Section 1201).
Injunctions matter. LinkedIn often seeks preliminary injunctions that can effectively shut down a service before final judgment.
Customers face indirect risk. When a scraping API gets sued or shut down, its customers lose data access. If your business depends on Proxycurl-style API data, you have business continuity risk.
For deeper context on the lawsuit, see our LinkedIn lawsuit guide.
The Browser-Based Middle Path
Between "expensive Sales Navigator subscription" and "lawsuit-prone unauthorized scraping," there's a legitimate middle path that many practitioners use:
Manual browsing with structured capture
- You log in to LinkedIn yourself
- You search and browse manually at human speed
- A browser tool captures structured data from pages you visit
- Export to CSV or JSON for your CRM, research, or outreach
This is what ScrapeMaster does. It's qualitatively different from automated scraping in three ways:
No autonomous requests. ScrapeMaster doesn't make HTTP requests to LinkedIn on its own. Your browser navigates; the extension captures what you see.
No bot patterns. Your traffic is human-paced and looks identical to any other LinkedIn user. No CAPTCHAs triggered, no rate limits hit.
No external server. All data lives in your browser. No cloud pipeline that can be subpoenaed or breached.
This isn't a workaround for LinkedIn's prohibitions — it's a fundamentally different category of tool. The User Agreement prohibits "automated means" and "bots." A browser extension that runs only when you click a button on a page you're already viewing isn't either of those things.
What ScrapeMaster fits
- Sales prospecting based on a list of target companies you actually research
- Recruiting research on candidates you actually browse
- Academic and journalistic research on public information
- Competitive analysis at human scale
- Personal CRM building from your existing connections
What ScrapeMaster doesn't fit
- Bulk extraction at scale (100,000+ profiles)
- Anonymous logged-out scraping at high volume
- Building a commercial API that resells LinkedIn data
- Anything that requires bypassing CAPTCHAs or rate limits
Comparison Table: API vs. Scraping vs. Browser Tools
| Approach | Cost | What's Allowed | Risk Profile | Scale |
|---|---|---|---|---|
| LinkedIn public API (basic) | Free (with limits) | Sign-in, share | None — sanctioned | Per-user only |
| Marketing API (MDP) | Partner approval required | Ad management for partners | None — sanctioned | Partner-scale |
| Talent / Sales API | Partner approval required | Recruiting / Sales integrations | None — sanctioned | Partner-scale |
| Sales Navigator | $100-160/user/month | Search, save leads, InMail | None — sanctioned | Mid-scale |
| Recruiter | Higher | Comprehensive recruiting | None — sanctioned | Enterprise |
| Unauthorized scraping (logged in) | "Free" | Nothing | High — User Agreement breach, lawsuits | Whatever you risk |
| Logged-out scraping | "Free" | Some public data per hiQ | Medium — CFAA protection but other claims | Limited |
| Commercial scraping API (Proxycurl, etc.) | $$ | Customer-facing API | High — service may be sued | Variable |
| Browser tools (ScrapeMaster) | Free | Manual collection | Low — not "automated means" | Per-session |
Other LinkedIn-Adjacent Tool Categories
There's a busy ecosystem of LinkedIn-related tools. A short comparison of common categories:
| Tool Type | Examples | Method | Risk |
|---|---|---|---|
| Browser extensions for connection export | LinkedIn's own export, browser PDF tools | Page-by-page or LinkedIn-sanctioned | Low |
| Browser extensions for outreach automation | Many | Often automated requests | Medium-High (account ban) |
| Cloud bulk scrapers | Octoparse, ParseHub, Apify | Scripted automation | High (User Agreement breach) |
| Commercial APIs from scraping providers | Proxycurl, et al. | Scraped data resold | High (lawsuits) |
| Browser-based manual capture | ScrapeMaster | Human browsing + structured capture | Low |
| LinkedIn's official tools | Sales Navigator, Recruiter | Sanctioned APIs | None |
The hiQ Precedent: What It Means for the API/Scraping Question
The hiQ v. LinkedIn line of cases held that scraping publicly-available data without logging in doesn't violate the CFAA. Several caveats:
- hiQ scraped without logging in. The User Agreement doesn't form because hiQ never agreed to it.
- hiQ ultimately went out of business — winning legal arguments isn't the same as winning commercially.
- hiQ-style logged-out scraping faces other legal theories beyond CFAA: copyright, breach of contract via terms posted on the site, anti-circumvention, state laws.
For most commercial use cases, hiQ doesn't provide reliable cover. It mostly addressed CFAA, didn't address contract claims fully, and the practical outcome of even a "winning" hiQ-style case was business closure.
Saving Your Compliance Reference Documents
Whatever path you choose, document your compliance position with PDFs of:
- LinkedIn's current User Agreement (it changes)
- LinkedIn's API documentation as of your decision date
- The specific endpoints/products you use
- Your partner agreement (if MDP/Talent/Sales)
- Any cease-and-desist correspondence
- Your internal policy on LinkedIn data handling
Convert: Web to PDF is built for this. It captures the page in front of you with a clean date stamp and no upload to any external service.
Frequently asked questions
Does LinkedIn have a public API for searching profiles?
No. LinkedIn's public API does not support searching across the LinkedIn member base. Profile search is available only through paid products like Sales Navigator and Recruiter.
What can the LinkedIn API actually do?
For most developers: Sign In with LinkedIn (OAuth authentication) and Share on LinkedIn (posting content). For approved partners: Marketing API, Talent API, Sales API, Compliance API — each requires partnership application and approval.
Is LinkedIn scraping legal?
LinkedIn's User Agreement explicitly prohibits scraping. Logged-in scraping is a clear contract violation. Logged-out scraping has some protection under hiQ v. LinkedIn (CFAA) but still faces copyright, anti-circumvention, and other claims. Multiple commercial scrapers have been sued.
Why does LinkedIn restrict its API so heavily?
LinkedIn's data is its core asset. Open API access at scale would commoditize that data. By restricting API access to specific approved partners and selling premium products like Sales Navigator and Recruiter, LinkedIn preserves the economic value of its member graph.
What's the cheapest sanctioned way to do LinkedIn-based prospecting?
Sales Navigator at ~$100-160/user/month is the typical entry-level sanctioned product for sales prospecting. For recruiting at scale, Recruiter is significantly more expensive. For free options, manual browsing with browser-based capture tools like ScrapeMaster is the legitimate low-cost approach.
Can I use a Chrome extension to export my LinkedIn connections?
Yes — LinkedIn's official data export (Settings → Data Privacy → Get a copy of your data) provides your connections list. Browser-based PDF tools like Convert: Web to PDF can also save individual pages of your network.
What happens if I use a third-party scraping service that gets sued?
Customer impact depends on the case. Often, the scraping service shuts down or significantly restricts data access, leaving customers without their data pipeline. There can also be legal exposure for customers if they knew the service was operating in violation of LinkedIn's terms.
Does ScrapeMaster connect to the LinkedIn API?
No. ScrapeMaster doesn't connect to any API. It captures structured data from pages you load yourself in your browser. There's no API key, no authentication beyond your normal LinkedIn session, and no requests made on your behalf.
What's the difference between Sales Navigator and Recruiter?
Sales Navigator is for outbound sales: lead search, saved lists, and InMail outreach. Recruiter is for hiring: candidate search, project pipelines, bulk InMail, and ATS integration. They have different feature sets and pricing.
How do I save the LinkedIn API documentation for reference?
Use Convert: Web to PDF on each documentation page. LinkedIn updates its API docs and product pages periodically; saving date-stamped PDFs lets you reference what was offered when you built your integration.
Bottom Line
LinkedIn's official API gives narrow, partner-controlled access. Sales Navigator and Recruiter are the sanctioned commercial products. Scraping is prohibited and actively litigated.
For most use cases, the practical landscape is: pay for Sales Navigator/Recruiter if you have budget, or use browser-based manual collection tools like ScrapeMaster for human-paced research. Avoid bulk scraping at scale and avoid commercial scraping APIs that LinkedIn is actively suing.
Save the User Agreement and API documentation as PDFs with Convert: Web to PDF so you have a date-stamped record of LinkedIn's terms and product offerings on the day you built or audited your integration. For long form analyses of LinkedIn legal cases, CineMan AI summarizes them inline so you can capture the implications quickly.