LinkedIn Profile Scraper (People)

Scrape public LinkedIn people profiles — one or many — into clean structured JSON: full name, headline, location, about/summary, work experience (title, company, dates), education, skills, profile photo, follower count and any publicly listed contact links. It reads LinkedIn's public profile page (the logged-out public_profile_v3 page that Google indexes), which embeds a rich schema.org Person JSON-LD block plus server-rendered Experience/Education/About sections — no login required for public data.

Requests use browser-grade HTTP fingerprints (got-scraping: real TLS + generated headers) routed through Apify Proxy. Residential IPs are tried first with a fresh session per retry; if LinkedIn throws an auth-wall, the actor automatically escalates to the Apify Proxy Unblocker group, which defeats heavier anti-bot protection.

Input

{
  "profileUrls": [
    "https://www.linkedin.com/in/williamhgates/",
    "satyanadella"
  ],
  "maxItems": 100,
  "useUnblocker": true,
  "proxyConfiguration": { "useApifyProxy": true, "apifyProxyGroups": ["RESIDENTIAL"] }
}

• profileUrls — LinkedIn people-profile URLs or bare vanity usernames (e.g. williamhgates). Required.
• maxItems — cap on how many profiles from the list to scrape (default 100).
• li_at — optional LinkedIn session cookie (yours, never someone else's). Leave empty for public-only scraping. Supplying it reduces auth-wall blocks and can reach gated profiles. Sent only as a request cookie; never logged or stored.
• useUnblocker — when residential attempts are auth-walled, retry via the Unblocker proxy group (default on).
• proxyConfiguration — Apify Proxy config; residential strongly recommended.
• timeoutSecs — per-request timeout in seconds (default 45).
• includeRawJsonLd — also attach the raw schema.org Person JSON-LD to each record.

Output (one record per profile)

{
  "source": "profile",
  "input": "https://www.linkedin.com/in/williamhgates/",
  "url": "https://www.linkedin.com/in/williamhgates",
  "scrapedVia": "residential",
  "authenticated": false,
  "fullName": "Bill Gates",
  "firstName": "Bill",
  "lastName": "Gates",
  "headline": "Chair, Gates Foundation and Founder, Breakthrough Energy",
  "location": "Seattle, Washington, United States",
  "country": "US",
  "about": "Chair of the Gates Foundation. Founder of Breakthrough Energy. Co-founder of Microsoft...",
  "photoUrl": "https://media.licdn.com/dms/image/.../profile-displayphoto...",
  "followers": 40681488,
  "connections": null,
  "currentJobTitles": ["Co-chair", "Founder", "Co-founder"],
  "experience": [
    { "title": "Co-chair", "company": "Gates Foundation", "companyUrl": "https://www.linkedin.com/company/gates-foundation", "dateRange": "2000 - Present 26 years", "location": null }
  ],
  "education": [
    { "school": "Harvard University", "degree": null, "dateRange": "1973 - 1975" }
  ],
  "skills": [],
  "languages": [],
  "email": null,
  "emailsFound": [],
  "websites": ["https://www.linkedin.com/in/williamhgates"]
}

Honest limitations

• Email / phone are almost never public. LinkedIn hides contact info behind login and (usually) a 1st-degree connection, so email is typically null. The actor still surfaces any genuinely public email/website it finds. To pull contact details you must supply your own li_at cookie, and even then some fields require being connected to the person.
• Skills and some sections are only present when the person exposes them publicly; when absent they come back as empty arrays.
• LinkedIn is one of the most aggressively defended sites on the web. Public-figure/creator profiles scrape reliably; low-profile or region-restricted accounts are more likely to hit an auth-wall — enable the Unblocker escalation or provide an li_at cookie for those.
• Use responsibly and in line with LinkedIn's terms and applicable law. Only scrape data you are permitted to access.