LinkedIn Profile Scraper: Extraction Workflow & Use Cases

Extracting profile data from LinkedIn requires matching the authentication method to profile visibility and selecting the right API fallback workflow. The Linkedin Profile Scraper processes profile URLs, handles, and partial paths using HTTP requests without browser overhead. Public profiles are scraped without authentication, while standard profiles use either a plain li_at session cookie or a full cookie JSON array. Missing fields are omitted rather than populated with nulls, producing structured JSON outputs for positions, education, skills, and recent articles.

Practical use cases

Use case 1: Executive team leadership mapping for account marketing

• Outcome: Extract structured current titles, past positions, education, and follower counts across executive leadership target lists.
• Question to answer: What are the historical career trajectories and current management responsibilities of key leaders at target organizations?
• Configure: Supply target profile handles or full URLs in profileUrls, set language to en, configure maxSkills to 25, and attach residential proxy settings in proxyConfiguration.
• Working method: Execute HTTP-only data extraction using public JSON-LD or Voyager API fallbacks to capture current positions, past positions, and education objects without browser rendering.
• Deliverable: A structured dataset with populated arrays for currentPositions, pastPositions, education, and followersCount.
• Stop condition: Stop execution when all specified profile URLs in profileUrls return scrapedAt timestamps and structured output objects.

Use case 2: Candidate skills verification for talent sourcing

• Outcome: Build structured arrays of verified candidate skills, job titles, and recent articles without login barriers for public profiles.
• Question to answer: Which technical skills and recent publication subjects exist on candidate profiles for specialized recruitment pipelines?
• Configure: Set profileUrls with candidate profile handles, enter a full cookie JSON array in cookie to access non-public regular profiles, set maxSkills to 50, and enable residential proxy rotation.
• Working method: Authenticate requests using full browser session replay (JSESSIONID, bcookie, li_at) to fetch structured skill arrays, certifications, and recent articles through the Voyager API interface.
• Deliverable: A candidate record table containing name, headline, skills array bounded by maxSkills, and recentArticles.
• Stop condition: Stop execution when every candidate profile URL is processed or logged as failed after trying Voyager API, JSON-LD, and meta tag extraction strategies.

Use case 3: Industry influencer activity tracking for content research

• Outcome: Benchmark publication frequencies, engagement metrics, and follower counts for public influencer profiles.
• Question to answer: How frequently do key industry leaders publish articles and what overall follower reach do they maintain?
• Configure: Set profileUrls with public influencer handles (such as satyanadella or in/reidhoffman), leave cookie blank for unauthenticated extraction, and select language as en.
• Working method: Send direct unauthenticated HTTP requests targeting public og:description meta tags and embedded JSON-LD scripts to pull headline, followers count, and article metadata.
• Deliverable: A normalized dataset containing followersCount, summary, recentArticles (with article titles, URLs, publish dates, and likes), and extractionSource flagged as json-ld.
• Stop condition: Stop execution when all public target profiles complete processing or reach the end of available recent articles.

Step-by-step extraction workflow

1. Prepare input URLs and handles: Collect target profiles as full URLs (https://www.linkedin.com/in/williamhgates), domain paths (linkedin.com/in/williamhgates), path fragments (in/williamhgates), or bare handles (williamhgates).
2. Select authentication mode: For public or influencer profiles, leave the cookie empty. For standard profiles, obtain the li_at cookie value from browser DevTools or export a full cookie JSON array via browser extensions like EditThisCookie.
3. Configure scraping parameters: Pass the target list into profileUrls, set maxSkills (between 1 and 200, default 25), set language (en, es, fr, de, pt), and assign proxy settings.
4. Execute extraction run: Launch the Linkedin Profile Scraper. The Actor executes HTTP requests and applies automatic fallback logic from Voyager API to JSON-LD parsing and meta tags.
5. Process omit-empty dataset: Retrieve dataset records. Non-existent fields are omitted from output objects instead of populating as null values. Analyze metadata including extractionSource, scrapedAt, and order.

Complementary Actors in the LinkedIn suite

Each Actor in the ecosystem targets a distinct LinkedIn surface or workflow requirement:

• Linkedin Profile Scraper: Scrapes LinkedIn public profiles without login to retrieve name, headline, experience, education, followers, and recent articles.
• LinkedIn Comments Scraper: Extracts all comments and reply threads on a post.
• LinkedIn Company Employees Scraper: Pulls the employee list for any company by URN.
• LinkedIn Company Info Scraper: Scrapes company About pages including size, HQ, industry, and specialties.
• LinkedIn Company Posts Scraper: Retrieves posts published from a company page.
• LinkedIn Events Scraper: Captures events by keyword or URL with full event detail.
• LinkedIn Hashtag Posts Scraper: Scrapes posts ranked under a specified hashtag.
• LinkedIn Jobs Scraper: Extracts job listings via the public jobs-guest API.
• LinkedIn Jobs Scraper Ultra: Extends job scraping with full detail enrichment.
• LinkedIn Learning Courses Scraper: Fetches the LinkedIn Learning course catalog by keyword.
• LinkedIn People Search Scraper: Executes people search using LinkedIn facets including role, company, school, and location.
• LinkedIn Post Reactions Scraper: Scrapes reactors on a post including name, headline, and reaction type.
• LinkedIn Post Scraper: Scrapes full post details including text, media, engagement counts, and author.
• LinkedIn Post Search Scraper: Finds posts matching keywords with date, author, and network filters.
• LinkedIn Profile Posts Scraper: Fetches all posts, reposts, and articles for one profile.
• LinkedIn Profile Scraper Pro: Extracts profile fields plus extra details such as recommendations, organizations, and languages.
• LinkedIn Profile Scraper Pro Ultra: Extracts Pro profile data along with premium fields like contact info and followers list when allowed.
• LinkedIn Profile Scraper Ultra: Captures profile data alongside the full upstream dash-120 surface.
• LinkedIn Profile Search by Name: Searches profiles by person name for matching CSV lists.
• LinkedIn Schools Alumni Scraper: Extracts alumni lists for any LinkedIn school page.
• LinkedIn Top Content Scraper: Collects trending and top-engagement posts by topic.
• LinkedIn User Activity Scraper: Scrapes reactions, comments, and post feeds for a single profile.

Operational limits and data quality

When processing profile extraction runs, keep the following operational constraints and data boundaries in mind:

• Contact information boundary: LinkedIn does not expose email addresses or phone numbers on public profile pages, and the Linkedin Profile Scraper only extracts data visible on the profile page.
• Session management and account safety: Authenticated runs using cookie credentials are subject to soft rate quotas from LinkedIn. It is recommended to use secondary accounts for high-volume jobs, along with proxy session rotation and request delays.
• Authentication requirements: Unauthenticated extractions work for public and influencer profiles through JSON-LD public previews. Standard non-public profiles require session credentials to extract detailed sections; without valid login cookies, non-public profiles fall back to auth-wall metadata returning basic details like name and headline.
• Omit-empty output structure: Missing or unpopulated profile fields are completely omitted from the output JSON record rather than returned with null values.
• Skill capping controls: The maxSkills parameter limits skill array length between 1 and 200 items (defaulting to 25).

Frequently asked questions

Do I need a LinkedIn cookie for every extraction run?

No. Public and influencer profiles can be extracted without a cookie using public JSON-LD previews and meta tags. Regular non-public profiles require providing a session cookie.

What is the difference between a plain li_at value and full cookie JSON?

The plain li_at string provides basic session authorization. The full cookie JSON array exported from browser extensions replays the entire session state, including JSESSIONID and bcookie, which provides better stability for authenticated requests.

How does the Actor handle missing profile fields?

Fields that cannot be extracted or are not populated on a profile are omitted from the output object entirely. No null values are inserted, keeping dataset schemas clean.

Can the scraper return private email addresses or phone numbers?

No. Email addresses and phone numbers are not exposed on public profile pages, and the scraper only extracts information visible on the profile page.

What fallback mechanisms ensure reliable extraction?

The scraper uses automatic multi-tier fallback strategies, moving from the Voyager API to JSON-LD parsing and finally to auth wall meta tags, ensuring maximum available data recovery.

How does maxSkills control dataset output?

The maxSkills input parameter sets an integer boundary (from 1 to 200, default 25) on how many listed skills are included in the output record.

Resources

• Linkedin Profile Scraper Actor on Apify
• LinkedIn Suite Actors Collection