LinkedIn Network Scraper

LinkedIn Network Scraper — Export Your Connections with Dates, Headlines & Profile URLs

Export your own LinkedIn network into a structured table. Every connection comes back with first and last name, headline, profile photo, vanity profile URL — and the exact date you connected, in both readable and ISO form.

Sorted most-recent-first, with optional date limits, so you can pull your whole network once and then run it daily to capture only what is new.

---

What is LinkedIn Network Scraper?

LinkedIn lets you download an archive of your connections, but it arrives hours later, as a static file, without headlines or photos, and with a date format that is awkward to work with.

This Actor reads your network through LinkedIn's own messaging-era API using your session cookie, page by page, most recent first — and returns each connection as a clean row with the connection date in both a human-readable form and an ISO YYYY-MM-DD field you can sort and filter directly.

Rows are saved as they are captured, so an interrupted run never loses what it already collected.

---

What data can you extract?

Field	Description
firstName, lastName	Connection's name
headline	Their current role and company, as shown on LinkedIn
vanityName	Profile slug (the /in/<slug> part)
url	Full profile URL
picture	Best available profile picture URL
connection_date	When you connected, human-readable
formated_connection_date	The same date in ISO format, for sorting and filtering
componentRef	Internal reference for the captured row

---

Why teams export their LinkedIn network

For sales and business development

Your accumulated network is usually your best-converting list, and it is trapped in an interface you cannot filter. Exporting it with headlines makes it searchable by role, industry and seniority in a spreadsheet.

For daily networking discipline

"Today only" mode plus a schedule creates an automatic networking journal: who you connected with, when, and what they do — captured on the day it happened, when you still remember the context.

For recruiters

A recruiter's network is the pipeline. Headlines and connection dates let you segment by specialisation and by how long you have known someone, which changes how you approach them.

For CRM import

Structured names, headlines and profile URLs drop straight into HubSpot, Pipedrive or a sheet — with the connection date as a genuine relationship-age field.

For analytics and reporting

formated_connection_date makes connection growth chartable: connections per month, growth after a conference, the effect of a content push.

For post-event follow-up

After a conference, run with a date limit covering that week and you have exactly the people you met, ready for a follow-up sequence.

---

How to export your network step by step

1. Sign in to LinkedIn in your browser.
2. Open DevTools (F12) → Application → Cookies → https://www.linkedin.com.
3. Copy the Value of the cookie named li_at.
4. Paste it into the Actor's LinkedIn li_at Cookie field.
5. Set a date limit if you only want recent connections, then click Start and export the Output tab.

---

⬇️ Input

Example input

{
  "liAtCookie": "<YOUR_LI_AT_COOKIE>",
  "waiting_time": 3,
  "date_limit_str": "2026-01-01"
}

Input reference

Field	Type	Default	Description
liAtCookie	string	— (required)	Your LinkedIn li_at session cookie. A full exported cookie session is also accepted for the most reliable authentication through proxies. Masked in the run interface.
starting_page	integer	1	Which page of your network to start from. Each page holds 40 connections — use this to resume a large export.
waiting_time	number	2	Polite pause between pages, in seconds. Random jitter is applied (your value → your value × 2) so the traffic pattern looks natural.
date_limit_today	boolean	false	Capture only the connections you added today.
date_limit_str	string	—	Stop once connections are older than this date (YYYY-MM-DD). Leave empty to export everything.
proxyConfiguration	object	Apify Proxy on	Starts direct and escalates to datacenter, then residential, only if LinkedIn pushes back. Configure residential country or groups here.

⚠️ Your cookie is your identity. li_at grants access to your LinkedIn account. Never share it, and be aware that automated activity can lead LinkedIn to restrict an account. Keep waiting_time conservative on large networks.

---

⬆️ Output

Example output

{
  "firstName": "Alex",
  "lastName": "Example",
  "headline": "Head of Growth at Example Analytics",
  "vanityName": "alex-example",
  "url": "https://www.linkedin.com/in/alex-example",
  "picture": "https://media.licdn.com/dms/image/…",
  "connection_date": "August 4, 2026",
  "formated_connection_date": "2026-08-04",
  "componentRef": "auto-component-6f1c…"
}

Illustrative values — a live run returns your own network data.

Rows are flat, so CSV and Excel exports open cleanly with no post-processing.

---

Usage recipes

Full network export

{
  "liAtCookie": "<YOUR_LI_AT_COOKIE>",
  "waiting_time": 3
}

Daily networking journal

{
  "liAtCookie": "<YOUR_LI_AT_COOKIE>",
  "date_limit_today": true
}

Save as a Task, attach a daily Schedule, and route the output to Google Sheets or Slack.

Catch up since your last export

{
  "liAtCookie": "<YOUR_LI_AT_COOKIE>",
  "date_limit_str": "2026-07-01"
}

Resume a large export

If a previous run stopped around connection 2,000 (50 pages × 40):

{
  "liAtCookie": "<YOUR_LI_AT_COOKIE>",
  "starting_page": 51,
  "waiting_time": 4
}

Segment your network by role

Export everything, then filter headline for the titles you sell to or recruit for. Sorting by formated_connection_date shows how long you have known each person — which is often the difference between a warm and a cold message.

---

How does this compare to LinkedIn's own data export?

LinkedIn's "Get a copy of your data" export gives you a connections CSV, but it is asynchronous (you wait for an e-mail), static, and limited in fields — no headlines, no photos, and a date format that is not directly sortable.

This Actor returns the same relationships on demand, with headlines and profile images included and the connection date in ISO form. It also supports incremental runs, which the official export does not: "today only" and "stop at date" mean a scheduled job costs almost nothing and captures only what changed.

There is also no LinkedIn API for reading your connections — the Connections API was deprecated long ago — so the official export is the only sanctioned alternative.

---

Integrate and automate

Python

from apify_client import ApifyClient

client = ApifyClient("<YOUR_APIFY_API_TOKEN>")

run = client.actor("scraperforge/linkedin-network-scraper").call(run_input={
    "liAtCookie": "<YOUR_LI_AT_COOKIE>",
    "date_limit_str": "2026-01-01",
    "waiting_time": 3,
})

for c in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(c["formated_connection_date"], c["firstName"], c["lastName"], "|", c["headline"])

JavaScript

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: '<YOUR_APIFY_API_TOKEN>' });

const run = await client.actor('scraperforge/linkedin-network-scraper').call({
    liAtCookie: '<YOUR_LI_AT_COOKIE>',
    date_limit_today: true,
});

const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

REST API

curl -X POST "https://api.apify.com/v2/acts/scraperforge~linkedin-network-scraper/runs?token=<YOUR_APIFY_API_TOKEN>" \
  -H "Content-Type: application/json" \
  -d '{"liAtCookie":"<YOUR_LI_AT_COOKIE>","date_limit_today":true}'

n8n, Make, Zapier and AI agents

Call the Actor from n8n, Make, Zapier or an MCP-capable agent — a daily "today only" run plus a Sheets append is the classic setup.

Schedules and webhooks

Attach a Schedule for a rolling network log, and use webhooks or the Google Sheets / Airtable / Slack integrations to move connections into your CRM automatically.

---

Pricing and what you are charged for

Pay-per-event: a small Actor-start charge plus a charge per connection row delivered. Date limits are the cheapest way to run continuously — a daily incremental run only pays for the handful of new connections it finds.

Current rates are on the Pricing tab of this Actor's page, and Apify shows an estimate before and during every run.

---

Limits, reliability and blocking

• This exports your network, not anyone else's. It reads the connections of whichever account the cookie belongs to.
• 40 connections per page. starting_page is measured in pages — multiply by 40 to work out where to resume.
• Cookies expire. If a run fails to authenticate, refresh li_at from your browser.
• Pace large networks. LinkedIn throttling shows up as a 302 redirect; the Actor treats that as a block signal and rotates through up to 6 fresh residential IPs, but persistent throttling means you should raise waiting_time.
• Challenge cookies are carried forward within a single IP context, which is what keeps a rotated session usable.
• No e-mail addresses or phone numbers. LinkedIn does not expose them through this route.
• Profile pictures are CDN URLs and expire — download them promptly if you need the files.
• Default run options are 4 GB memory and a 1-hour timeout; raise the timeout for very large networks.

---

Is it legal to export your LinkedIn connections?

This Actor accesses your own LinkedIn network using your own session, in the same way your browser does. It does not access other people's private data or bypass any protection, and LinkedIn itself provides an official export of the same relationships.

Your connections' names, headlines and photographs are still personal data about other people. If you import them into a CRM or use them for outreach, you need a lawful basis under GDPR and comparable regimes, must honour opt-outs, and should keep the data secure and access-controlled. Automated access can also lead LinkedIn to restrict an account under its User Agreement — that risk is yours.

---

❓ Frequently asked questions

Do I need my LinkedIn password?

No — only the li_at session cookie, copied from your own browser.

Where exactly do I find li_at?

Sign in to linkedin.com → DevTools (F12) → Application → Cookies → https://www.linkedin.com → copy the Value of li_at.

Is my cookie stored?

It is used only to authenticate the requests in your own run, and it is masked in the run interface. Treat it like a password regardless.

Can I export someone else's connections?

No. LinkedIn only exposes your own network to you, and this Actor does not attempt anything else.

How do I get only new connections?

Turn on date_limit_today for today's additions, or set date_limit_str to the date of your last export.

Why did the run stop early?

Either a date limit was reached — which is expected — or LinkedIn throttled the session. The log reports proxy escalations and blocks explicitly.

Can I get connections' e-mail addresses?

No. That data is not available through this endpoint.

How is this better than LinkedIn's own export?

It is on demand rather than asynchronous, includes headlines and photos, gives you an ISO connection date, and supports incremental runs.

Which export format should I use?

CSV or Excel — the rows are flat and load directly into a spreadsheet or CRM importer.

---

🔗 Related scrapers

• LinkedIn Conversation Scraper — your inbox threads, with follow-up recency built in.
• LinkedIn Open Profile Status — check which of your connections are openly job-hunting.
• LinkedIn Company Employees Scraper — expand beyond your network into target accounts.
• Leads Scraper — verified e-mails and phones for the people you identify.

Browse the full collection on the ScraperForge profile.

---

💬 Feedback

Need extra fields, faster pagination, or a custom network-analytics pipeline? Open an issue on the Issues tab of this Actor.