🔗 LinkedIn Network Scraper

Export your LinkedIn 1st‑degree connections in seconds — names, headlines, profile URLs, pictures, and the exact date you connected. Clean JSON / CSV / XLSX, no manual export needed.

---

✨ Why Choose Us?

• 🍪 Just paste your cookie — no fragile email/password flows.
• 👥 Bulk accounts supported — pass multiple li_at cookies and the actor processes each account in turn.
• 📅 Date filters that actually stop early — only today's connections, or only since 2025‑01‑01.
• 🛡️ Smart proxy escalation — direct first, datacenter on block, residential as last resort (with 3 retries).
• 💾 Real‑time saving — every page lands in the dataset immediately, so a hiccup mid‑run still leaves you with results.
• 🪶 Lightweight — pure HTTP (no headless browser), runs cheap and fast.

---

🚀 Key Features

Feature	Detail
🔗 1st‑degree export	Pulls everyone in your network, newest first
🍪 Bulk cookies	Run multiple accounts in a single job
📅 Date cutoff	Today only or Since YYYY‑MM‑DD
⏱️ Friendly pacing	Configurable delay + jitter
📦 Page size	1–40 per request
🛡️ Proxy fallback	none → datacenter → residential (3 retries)
💾 Live dataset push	Partial results never lost
📊 Table view	Pretty Apify Console output with profile pictures

---

🧾 Input

{
  "liAtCookies": [
    "AQEDAUjBCq4FO9swAAAB..."
  ],
  "startingPage": 1,
  "pageSize": 40,
  "maxConnections": 0,
  "waitingTime": 2.0,
  "dateFilterMode": "any",
  "dateLimit": "",
  "proxyConfiguration": { "useApifyProxy": false }
}

Field reference

Field	Type	Meaning
liAtCookies	string[]	One or more LinkedIn li_at cookies. Each cookie is one account. Required.
startingPage	integer	Page to start from (1 = newest). Default 1.
pageSize	integer	Items per request, 1–40. Default 40.
maxConnections	integer	Per‑cookie cap. 0 = no cap. Default 0.
waitingTime	number	Base delay (seconds) between pages. Random jitter added in code. Default 2.0.
dateFilterMode	enum	any / today / sinceDate.
dateLimit	string	ISO date (YYYY‑MM‑DD). Only used with sinceDate.
proxyConfiguration	object	Apify proxy config. Off by default.

🍪 How to get your li_at cookie

1. Sign in to linkedin.com.
2. Open DevTools → Application → Cookies → https://www.linkedin.com.
3. Copy the value of the li_at cookie.
4. Paste it into liAtCookies.

---

📤 Output

Each row in the dataset:

{
  "vanityName": "sarafathossen",
  "firstName": "Sarafat",
  "lastName": "Hossen",
  "componentRef": "auto-component-72360a4e-59f5-464a-8206-7e55512cc5fd",
  "connection_date": "Connected on May 10, 2026",
  "formated_connection_date": "2026-05-10",
  "picture": "https://media.licdn.com/dms/image/v2/.../profile.jpg",
  "headline": "MERN Stack Developer | React, Node.js, MongoDB",
  "url": "https://www.linkedin.com/in/sarafathossen"
}

Field	Description
vanityName	Public profile slug (linkedin.com/in/<vanityName>)
firstName / lastName	Display name
componentRef	Stable per‑row UUID (useful when joining data)
connection_date	Human‑readable: "Connected on May 10, 2026"
formated_connection_date	ISO date (YYYY‑MM‑DD) — easy to sort/filter
picture	Highest‑resolution profile photo URL (null if none)
headline	The contact's current headline
url	Full profile URL

---

🚀 How to Use (Apify Console)

1. Log in at console.apify.com → Actors.
2. Open this actor (LinkedIn Network Scraper).
3. Paste your li_at cookie in 🍪 LinkedIn li_at Cookie(s) (add more for bulk).
4. (Optional) Configure starting page, page size, max items, delay, date filter.
5. Click Start ▶️.
6. Watch the live log — connections stream in as they're scraped.
7. Open the 📂 Output tab to preview / export as JSON / CSV / XLSX.

---

🤖 Use via API

curl -X POST "https://api.apify.com/v2/acts/<ACTOR_ID>/run-sync-get-dataset-items?token=$APIFY_TOKEN" \
     -H "Content-Type: application/json" \
     -d '{
       "liAtCookies": ["AQEDAU..."],
       "pageSize": 40,
       "dateFilterMode": "any"
     }'

Asynchronous run:

curl -X POST "https://api.apify.com/v2/acts/<ACTOR_ID>/runs?token=$APIFY_TOKEN" \
     -H "Content-Type: application/json" \
     -d '{"liAtCookies": ["AQEDAU..."]}'

---

🎯 Best Use Cases

• 📇 CRM enrichment — push your network into HubSpot / Salesforce / Notion.
• 📧 Outbound campaigns — build segmented lists by headline / connection date.
• 📊 Reporting — see who you connected with this week / month / quarter.
• 🧠 Personal knowledge graph — back up your network outside LinkedIn.
• 🔍 Recruiting — surface relevant contacts by headline keywords.

---

💵 Pricing

This actor uses the Pay‑Per‑Result model on Apify Store. You only pay for the connections actually saved to your dataset — failed runs and skipped rows are free.

Tip: lower the Page Size or raise the Delay if LinkedIn rate‑limits aggressively. Proxy escalation is automatic.

---

❓ Frequently Asked Questions

Q: Do I need to log in via email/password? A: No — just paste your li_at cookie. It's the only credential the actor needs.

Q: Is my cookie stored anywhere? A: It lives only in your run's input. Apify never logs cookie values in the run log.

Q: Will this scrape other people's networks? A: No. LinkedIn's API only returns the connections of the account whose cookie is provided.

Q: How many connections per minute? A: Roughly 40 per request, paced with a random delay (default ~2s). Adjustable.

Q: What happens if LinkedIn blocks me? A: The actor escalates: direct → datacenter proxy → residential proxy (3 retries). It logs the switch transparently.

Q: Why are some last names empty? A: LinkedIn returns "undefined" for accounts without a last name set — the actor normalizes this to an empty string (mirrors the source script).

---

🆘 Support & Feedback

Have an idea or need a custom version? 📧 dev.scraperengine@gmail.com

Found a bug? Open an issue on the actor page and include the run ID — we'll take a look.

---

⚖️ Cautions / Legal

• 📜 Use only with accounts you own or are authorized to scrape.
• 🛡️ Respect LinkedIn's Terms of Service and applicable laws (GDPR, CCPA).
• 🤝 The end user is responsible for compliance — please be a good citizen.