LinkedIn Profile Scraper

The Actor resolves one or more public LinkedIn profiles to structured records containing headline, location, about text, work history, education, articles, and recent activity. It accepts either bare usernames or full /in/ profile URLs, and requires no LinkedIn account or session cookie.

Accepted input

Field	Type	Default	Description
username	array of strings	—	Required. LinkedIn usernames or /in/ profile URLs.
maxItems	integer	100	Maximum profiles fetched. 0 removes the limit.

{
  "username": [
    "williamhgates",
    "https://www.linkedin.com/in/satyanadella/"
  ],
  "maxItems": 100
}

Both forms shown above are equivalent. A value is reduced to its /in/ segment before the request is made, so country subdomains (uk.linkedin.com), trailing slashes, query strings, and a leading @ are all accepted and stripped. Duplicate entries that reduce to the same username are removed before any request is issued, and are therefore neither fetched nor billed twice.

Response fields

One record per profile.

Field	Contents
username	The username used to fetch the record
name	Name displayed on the profile
headline	Headline or organisation text
job_titles	Job titles listed on the profile
badges	Profile badges, such as open-to-work
location	Location text as displayed
country	Country component of the location
about	About section
followers	Follower count
connections	Connection count
image	Profile image URL
url	Canonical profile URL
languages	Languages listed
awards	Awards listed
works_for	Current organisation
experience	Work history entries
education	Education entries
education_jsonld	Education as published in the page's structured data
articles	Articles authored by the member
related_profiles	Profiles LinkedIn shows alongside this one
activity	Recent public activity
jsonld	The page's raw JSON-LD block

{
  "username": "williamhgates",
  "name": "Bill Gates",
  "headline": "Chair, Gates Foundation",
  "location": "Seattle, Washington",
  "country": "United States",
  "followers": 37000000,
  "url": "https://www.linkedin.com/in/williamhgates"
}

Behaviour on partial results

Profiles are fetched one request per username. A username that cannot be retrieved — because the profile is private, has been removed, or the request failed after the client's own retries — is logged as a warning and skipped. The run continues to the next username and completes normally, so one unreachable profile does not discard the profiles collected before it or prevent those after it from being fetched.

A profile that is not publicly visible therefore produces no record rather than a partial one. The number of records returned can consequently be lower than the number of usernames supplied, and the run log lists every username that was skipped.

Fields absent from the source profile are returned as null rather than omitted, so the record shape is stable across a run.

Frequently asked questions

Is a LinkedIn account or session cookie required? No. The Actor reads publicly visible profile pages only. No LinkedIn credentials, li_at cookie, or logged-in session is supplied or needed, which also means nothing is tied to a personal account.

Are email addresses returned? No. Email addresses are not published on public LinkedIn profiles, and none are inferred, guessed, or looked up through third-party sources. The record contains what the public page displays.

Why does a profile return fewer fields than expected? Members control the visibility of individual sections. An about section, education list, or activity feed hidden from logged-out visitors is absent from the page the Actor reads, and the corresponding field is null. Signed-in visibility is not reproduced.

What distinguishes related_profiles here from the Related User Scraper? This Actor returns the related-profile list as one field on the profile record. LinkedIn Related User Scraper expands the same list into one row per related person, deduplicated across seeds, with optional full profile detail for each. Use this Actor when the seed profile is the subject; use that one when the related people are.

Can a profile URL be supplied instead of a username? Yes, and the two are interchangeable. Regional subdomains, trailing slashes, and query strings are removed before the request.

How many profiles can one run fetch? As many usernames as are supplied, bounded by maxItems. Each profile is a separate request, so the run duration scales linearly with the number of usernames.

Related Actors

Actor	Purpose
LinkedIn Related User Scraper	Expand a seed profile into the people LinkedIn shows alongside it
LinkedIn Company Scraper	Company page details by handle or URL
LinkedIn Post Scraper	Post, activity, and article details by URL
LinkedIn Jobs Scraper	Job search by keyword and location