LinkedIn Post Scraper (no cookies) avatar

LinkedIn Post Scraper (no cookies)

Pricing

from $3.00 / 1,000 results

Go to Apify Store
LinkedIn Post Scraper (no cookies)

LinkedIn Post Scraper (no cookies)

Scrapes the details of a single public LinkedIn post — text, author, reactions, comment count and top comments — without a session cookie.

Pricing

from $3.00 / 1,000 results

Rating

0.0

(0)

Developer

Mina

Mina

Maintained by Community

Actor stats

1

Bookmarked

2

Total users

1

Monthly active users

3 days ago

Last modified

Share

LinkedIn Post Scraper

What does LinkedIn Post Scraper do?

Give it a link to a public LinkedIn post and it returns that post's details as structured data — the text, who wrote it, when it was published, how many reactions and comments it has, and any image or video attached.

No LinkedIn account, login, or cookie is needed. Paste a link, press Start, and download the result as JSON, CSV or Excel — or pull it straight from the Apify API.

Why use LinkedIn Post Scraper?

  • Track performance — record reactions and comments on a post, and run it again later to see how they grew.
  • Archive posts — keep a copy of the text, author and media of posts that matter to you.
  • Build reports — the output is flat and predictable, so it drops straight into a spreadsheet or database.
  • Monitor accounts — collect the numbers on any public post from your team, your competitors, or your industry.

How to use LinkedIn Post Scraper

  1. Paste one or more LinkedIn post URLs into the input.
  2. Optionally tick Fetch comments and follower count if you want those too.
  3. Click Start.
  4. When the run finishes, open the Output tab to preview the data or export it.

All of these point at the same post, and any of them is accepted:

https://www.linkedin.com/posts/williamhgates_some-slug-activity-7482647567445495808-9S6u
https://www.linkedin.com/feed/update/urn:li:activity:7482647567445495808/
urn:li:activity:7482647567445495808
7482647567445495808

The easiest way to get one: open the post on LinkedIn, click the menu in its top-right corner, and choose Copy link to post.

Input

FieldTypeRequiredDescription
LinkedIn post URLs (post_urls)arrayYesOne or more post links.
Fetch comments and follower count (include_comments)booleanNoAdds the top comments, the author's follower count and the video length. Slower. Off by default.
Max concurrent requests (max_concurrency)integerNoHow many posts to fetch at once. Default 1.
Include raw data (include_raw)booleanNoAdds the unprocessed page data to each record, for debugging. Off by default.

Example input:

{
"post_urls": [
"https://www.linkedin.com/feed/update/urn:li:activity:7482647567445495808/"
],
"include_comments": true
}

Output

One record per post you submit:

{
"post_url": "https://www.linkedin.com/feed/update/urn:li:activity:7482647567445495808",
"activity_id": "7482647567445495808",
"post_type": "video",
"text": "Nuclear fission and fusion could give the world virtually unlimited clean energy.",
"published_at": "2026-07-14T04:10:00Z",
"reaction_count": 4150,
"comment_count": 403,
"author_name": "Bill Gates",
"author_headline": "Chair, Gates Foundation and Founder, Breakthrough Energy",
"author_profile_url": "https://www.linkedin.com/in/williamhgates",
"author_avatar": "https://media.licdn.com/dms/image/v2/…",
"author_followers": 40573405,
"images": [],
"video_url": "https://dms.licdn.com/playlist/vid/v2/…",
"video_thumbnail": "https://media.licdn.com/dms/image/v2/…",
"video_duration": "PT2M32S",
"comments": [
{
"text": "Demystifying the science behind fission and fusion",
"author_name": "Bill Gates",
"published_at": "2026-07-14T04:10:26Z",
"like_count": 12
}
],
"is_unavailable": false,
"error": null
}

You can download the dataset in various formats such as JSON, HTML, CSV, or Excel.

Data fields

FieldDescription
post_urlLink to the post.
activity_idLinkedIn's own id for the post.
post_typepost for text and images, video for a native video.
textThe post as written.
published_atWhen it was posted.
reaction_countTotal reactions.
comment_countTotal comments.
author_nameWho posted it.
author_headlineTheir job title line.
author_profile_urlLink to their profile.
author_avatarTheir profile photo.
author_followersTheir follower count. Needs Fetch comments and follower count.
imagesImages attached to the post.
video_urlDirect link to the video file, if the post has one.
video_thumbnailThe video's cover image.
video_durationHow long the video is. Needs Fetch comments and follower count.
commentsTop comments, each with its author, text, date and likes. Needs Fetch comments and follower count.
is_unavailabletrue if the post is deleted or not public.
errorFilled in only if something went wrong with that link.

What it cannot return

  • The full comment thread. LinkedIn shows only the top handful of comments publicly. comment_count is the true total; comments is the visible sample.
  • A breakdown of reactions. You get the total, not the split between Like, Celebrate, Insightful and so on.
  • Private or deleted posts. These come back with is_unavailable: true.

How much does it cost to scrape LinkedIn posts?

Very little. A typical post costs a fraction of a cent, and a batch of five finishes in about twenty seconds. Ticking Fetch comments and follower count roughly doubles the work per post.

Tips

  • Leave Max concurrent requests at 1 unless you are in a hurry. LinkedIn limits how fast anyone can read, and going faster mostly means more retries.
  • Batch your links into one run instead of starting a separate run per post.
  • Only tick Fetch comments when you need them — without it, runs are faster and cheaper.

FAQ and support

Do I need a LinkedIn account or cookie? No. Nothing to log in with and nothing to keep alive.

Why is comments shorter than comment_count? LinkedIn only publishes the top few comments to people who are not signed in. The count is the real total.

Why did a post come back as unavailable? It was deleted, made private, or its author limited who can see it.

Is scraping LinkedIn legal? This Actor collects only publicly available data. You are responsible for how you use it, and you should not collect personal data without a legal basis. If in doubt, take legal advice.

Found a bug, or need a field that is not here? Open an issue on the Issues tab.