LinkedIn Profile Scraper (No Cookies) — Full Extraction

Get the maximum public footprint of any LinkedIn profile from just its URL — no login, no session cookie, no browser setup. For each profile this Actor aggregates every no-cookie data surface LinkedIn exposes into one comprehensive record: full profile sections, the person's posts, their comments, their reactions, and a best-effort raw-HTML capture.

Runs on the Apify platform — API access, scheduling, integrations, and monitoring included.

What it collects

For every profile URL you pass in, the output record contains:

• profile — every populated profile section: name, headline, about, location, current company, follower/connection counts, verification flags, experience, education, certifications, skills, languages, honors, and (optionally) a work email.
• posts — the person's posts/activity: text, media, URLs, timestamps, and full reaction breakdowns (likes, celebrate, support, love, insightful, …).
• comments — comments the person left, each with the post it was left on.
• reactions — posts the person reacted to, with the reaction, the post, and its author.
• html — a best-effort fetch of the public profile HTML via an Apify residential proxy, with any JSON-LD and Open Graph tags parsed and the raw bytes saved to the key-value store. Note: logged-out LinkedIn almost always returns an auth wall (HTTP 999) with no profile data — the structured sections above are the true no-cookie maximum; this field exists for completeness and transparency.
• counts / sources — per-section counts and provenance for every datapoint.

Under the hood it delegates each surface to the corresponding no-cookie Actor by apimaestro (profile full-sections, batch posts, comments, reactions) and merges the verbatim results by username. No LinkedIn credentials are ever used.

Why use it?

Logged-out LinkedIn profile pages are auth-walled, so scraping them yourself returns nothing. This Actor gives you URL in → everything out: lead enrichment, recruiting/sourcing, CRM hydration, competitor and activity analysis, and people datasets — all cookie-free.

How to use

1. Open the Input tab.
2. Paste one or more profile URLs into LinkedIn profile URLs (e.g. https://www.linkedin.com/in/aymaneelhattab). Bare usernames work too.
3. Toggle which sections you want (profile is always fetched; posts / comments / reactions / email / HTML are optional) and set the activity limit.
4. Click Start. Each profile becomes one rich record in the dataset.

Input

Field	Type	Default	Description
profileUrls	array	—	Profile URLs or usernames (required).
includeEmail	boolean	true	Resolve a work email per profile.
includePosts	boolean	true	Scrape posts / activity.
includeComments	boolean	true	Scrape comments the person left.
includeReactions	boolean	true	Scrape posts the person reacted to.
activityLimit	integer	100	Max posts / comments / reactions per profile.
fetchHtml	boolean	true	Best-effort raw HTML fetch (usually an auth wall).

{
    "profileUrls": ["https://www.linkedin.com/in/aymaneelhattab"],
    "includeEmail": true,
    "includePosts": true,
    "includeComments": true,
    "includeReactions": true,
    "activityLimit": 100,
    "fetchHtml": true
}

Output

One dataset item per profile. Download as JSON, CSV, Excel, or HTML.

{
    "username": "aymaneelhattab",
    "full_name": "Aymane Elhattab",
    "profile_url": "https://www.linkedin.com/in/aymaneelhattab",
    "scraped_at": "2026-07-02T13:20:00+00:00",
    "profile": {
        "basic_info": { "headline": "Engineering Manager @Appstronaute", "current_company": "Appstronaute", "location": { "full": "Marseille, France" }, "follower_count": 1375, "email": null },
        "experience": [ { "title": "Engineering Manager", "company": "Appstronaute", "is_current": true } ],
        "education": [],
        "languages": [ { "language": "English", "proficiency": "…" } ]
    },
    "posts": [ { "text": "Looking for talented React Native developers…", "posted_at": {"date": "2026-02-15 17:06:31"}, "stats": { "total_reactions": 38, "comments": 2, "reposts": 1 } } ],
    "comments": [ { "comment_text": "Nice 🚀", "post": { "…": "…" } } ],
    "reactions": [ { "action": "like", "post_url": "https://www.linkedin.com/…", "author": { "…": "…" } } ],
    "html": { "http_status": 999, "blocked": true, "raw_html_key": "html-aymaneelhattab", "json_ld": [], "meta": {}, "note": "LinkedIn served an auth wall to the logged-out request." },
    "counts": { "experience": 5, "posts": 3, "comments": 1, "reactions": 74 }
}

Main data fields

Field	Description
profile.basic_info	Name, headline, about, location, company, counts, flags, email.
profile.experience / education / certifications / languages / skills	All populated profile sections.
posts	Posts with text, media, timestamps, and reaction breakdowns.
comments	Comments left by the person + their parent posts.
reactions	Posts the person reacted to + reaction type.
html	Raw HTML capture summary + parsed JSON-LD / OG (key-value store holds raw bytes).
counts / sources	Per-section counts and data provenance.

Cost

Billed per result by the underlying no-cookie Actors (about $0.005 per profile for details, plus a small per-item cost for posts / comments / reactions). Raising activityLimit fetches more activity and costs more. Apify's free monthly credit is enough for hundreds of fully-enriched profiles.

Tips

• Batch many URLs into profileUrls — sources run once for the whole batch.
• Turn off includeReactions or lower activityLimit to cut cost on high-activity profiles.
• Turn off fetchHtml to skip the (usually auth-walled) HTML fetch entirely.

FAQ, disclaimers & support

• Do I need a LinkedIn account or cookie? No — fully cookieless.
• Why is html an auth wall? LinkedIn blocks logged-out profile page requests (HTTP 999). No public HTML is available without a session; the structured sections are the no-cookie maximum.
• A profile returned little data. The person may not expose those sections publicly, or the username is wrong/private.
• Legality: only public data is accessed. You are responsible for compliant use (LinkedIn Terms, GDPR/CCPA).