All help articles
How-to guidesUpdated 5/13/2026

How to scrape LinkedIn profiles safely (2026 guide)

LinkedIn is the single richest source of B2B lead data on the open web — and the hardest to scrape because they aggressively block bots. On Kavex you scrape with your own LinkedIn session cookie, which means our requests look identical to your normal browsing. We never see your password, the cookie is encrypted at rest, and you can remove it anytime.

This guide covers the safe way to do it: which fields you can pull, how the cookie flow works, and how Kavex compares to Phantombuster and direct-DIY approaches.

Start free (your own cookie, AES-encrypted)

No credit card. Use any service for the equivalent free credit value.

Get started

What you can pull from a LinkedIn profile

Kavex extracts up to 26 fields per profile when you enable all toggles. Always-included fields: name, headline, location, current company.

Why you need a cookie

LinkedIn locks profile pages behind a login wall. Without a session cookie, every request to /in/username gets a "Sign Up" wall and zero data. The cookie tells LinkedIn "this is a real session" so the full profile renders.

You provide your own li_at cookie (the same one your browser uses). We encrypt it with AES-256-GCM and only decrypt it on the scraper at run time — never expose it in the UI, never log it, never send it back to your browser.

Step-by-step scrape

Once your cookie is saved, scraping is a paste-and-go flow.

How is this different from Phantombuster?

Phantombuster bills per-execution-time (€56-€352/month for hours of phantom usage). Kavex bills per-result (3 credits = $0.003 per profile). On a typical 500-profile recruiting list, Phantombuster runs through 30+ minutes of phantom time; Kavex finishes in 1.5k credits ($1.50). The savings compound on regular use.

Tools mentioned in this guide

How Kavex compares to alternatives

We don't hide from comparisons. Each link below is an honest side-by-side breakdown.

Frequently asked questions

Will my LinkedIn account get banned?

We rate-limit aggressively (one request every 2.5-5.5 seconds with sticky proxy IPs), so for normal-volume use the risk is low. We recommend keeping your daily scrape volume under ~200 profiles per cookie. Heavier users should rotate cookies (sub-accounts).

How do I get my li_at cookie?

Open linkedin.com → DevTools (F12) → Application → Cookies → linkedin.com → copy the value of li_at. The /settings page in Kavex has step-by-step screenshots.

What happens when the cookie expires?

LinkedIn rotates session tokens every 30-90 days. We auto-test the cookie on every Settings visit and auto-delete it when invalid — you'll see a banner asking you to paste a fresh one.

Can I scrape someone else's LinkedIn data?

Only what they've made public on their own profile. We don't bypass any privacy settings — if a profile is private, you'll see only what a logged-in visitor sees.

Keep reading

Ready to try Kavex?

1,000 free credits on signup. No credit card.

Get started