Use Cases 4 min read

Proxies for LinkedIn Public Data: What's Allowed and a Responsible Setup

LinkedIn is one of the most restrictive sites to collect data from. Start with the official routes, and if you do fetch public pages, do it slowly and politely.

Recruiters, sales teams and researchers ask about proxies for LinkedIn public data more than almost any other site. Before any setup advice, the honest context: LinkedIn's User Agreement prohibits scraping and automated access, LinkedIn actively enforces it, and collecting data about people raises privacy obligations in many countries. A proxy changes your IP; it does not change any of that.

So this guide is ordered by what you should try first. Proxies come last, for narrow, low-volume access to public, logged-out pages, after you have read the terms and taken advice where needed. Our article on whether proxies and scraping are legal gives the general background.

Step 1: Use the Official Routes

  • LinkedIn's own products for recruiting, sales and marketing give licensed access to data inside the platform's rules.
  • LinkedIn's developer APIs cover specific use cases for approved partners; check whether yours qualifies.
  • For company information, the company's own website, press releases and public filings are often more accurate than a LinkedIn page anyway.
  • For job market research, many employers publish openings on their own career pages - see proxies for job listings data.

Step 2: Never Automate Logged-In Accounts

Running scripts through a logged-in LinkedIn account - your own or anyone else's - is the clearest breach of the terms and the fastest way to get the account restricted. It also pulls in data that is only visible because you agreed to the terms as a member. Do not do it, with or without proxies.

Step 3: If You Fetch Public Pages, Be Polite

Some public, logged-out pages - for example company pages or individual job postings that LinkedIn makes available to search engines - can be viewed by anyone. If, after checking the terms and the law in your jurisdiction, you decide to fetch a small number of these, build politeness into the code rather than relying on good intentions. This fetcher checks robots.txt before every URL, refuses anything disallowed, and waits between requests:

import time, random, requests
from urllib import robotparser
from urllib.parse import urlparse

PROXY = 'http://USERNAME-country-us:[email protected]:8080'
UA = 'ResearchBot/1.0 (contact: [email protected])'
_robots = {}

def allowed(url):
    host = urlparse(url).scheme + '://' + urlparse(url).netloc
    if host not in _robots:
        rp = robotparser.RobotFileParser()
        r = requests.get(host + '/robots.txt', headers={'User-Agent': UA},
                         proxies={'http': PROXY, 'https': PROXY}, timeout=20)
        rp.parse(r.text.splitlines())
        _robots[host] = rp
    return _robots[host].can_fetch(UA, url)

def polite_get(url):
    if not allowed(url):
        print('robots.txt disallows', url, '- skipping')
        return None
    time.sleep(random.uniform(8, 15))
    r = requests.get(url, headers={'User-Agent': UA},
                     proxies={'http': PROXY, 'https': PROXY}, timeout=30)
    if r.status_code in (429, 999):
        print('Rate limited - stopping for today')
        return None
    return r.text

A few deliberate choices here. The User-Agent identifies your bot and gives a contact address instead of pretending to be a browser. The delay is long. And when the site signals rate limiting (LinkedIn commonly answers automated traffic with an unusual status code 999), the script stops for the day instead of switching IPs and trying harder. If robots.txt disallows your user agent entirely, the script fetches nothing - which is the correct outcome.

What Proxies Actually Do Here

In this narrow setup, a proxy does two legitimate things. It keeps research traffic off your office IP, so your colleagues' normal LinkedIn use is not affected by a script. And country targeting lets you see a public page as it appears in a given market, since LinkedIn localizes language and some content. It should not be used to spread thousands of requests across thousands of IPs to evade limits; that is exactly the behaviour the terms prohibit.

Which proxy type

For low-volume public page checks, residential proxies behave like a normal visitor. At the volume described here, bandwidth is tiny - a 100 MB plan lasts a long time. Datacenter IPs tend to meet login walls on LinkedIn more often.

Handling Personal Data

Profiles contain personal data. If you are in or targeting the EU or UK, data protection law applies even to public information: you need a lawful basis, must minimise what you keep, and must honour deletion requests. Collect only the fields you need, store them securely, set a retention period, and never build contact lists for unsolicited marketing from scraped profiles.

Using NodeProxies for This

If your use passes the checks above, register, add a few dollars by card or crypto (minimum $3), and buy a small residential plan. Use plain country targeting like USERNAME-country-us for single page loads. There is no subscription to cancel and no ID verification. See the pricing page for per-GB rates.

FAQ

Is scraping LinkedIn legal?

It depends on the jurisdiction, what data you collect and how. It does break LinkedIn's User Agreement, which LinkedIn enforces. Get legal advice before any project at scale.

What does LinkedIn error 999 mean?

LinkedIn often returns status 999 to traffic it considers automated. Treat it as a signal to stop, not to rotate to new IPs.

Can I use proxies with my LinkedIn account?

Using a single stable connection for normal manual use is fine; automating a logged-in account is against LinkedIn's terms whatever IP you use.

NodeProxies

Ready to get started?

90M+ residential, mobile & datacenter proxies. Datacenter from $0.30/GB, residential from $0.42/GB. No contracts.

Create free account