LinkedIn Post Comments Scraper (No Cookies) avatar

LinkedIn Post Comments Scraper (No Cookies)

Pricing

from $1.50 / 1,000 comment scrapeds

Go to Apify Store
LinkedIn Post Comments Scraper (No Cookies)

LinkedIn Post Comments Scraper (No Cookies)

Comments, replies and everyone who reacted on any public LinkedIn post. No cookies or login. Per-comment reaction breakdown, post-author flag, thread position, keyword and recency filters.

Pricing

from $1.50 / 1,000 comment scrapeds

Rating

0.0

(0)

Developer

Capable Cauldron

Capable Cauldron

Maintained by Community

Actor stats

1

Bookmarked

2

Total users

1

Monthly active users

3 days ago

Last modified

Features

Limited permissions

Share

This LinkedIn post comments scraper collects comments, replies and reactions from any public post link and exports them as JSON, CSV or Excel, with no LinkedIn login or cookies. Paste one or more post URLs, say how many comments you want, and every row comes back with the commenter's name, headline, profile URL, the comment text, a 7-way reaction breakdown and a flag telling you whether the post author wrote it. Turn on reactions and you also get the people who liked or celebrated the post without commenting.

Built on Apify, so you can schedule runs, call it from the API or a webhook, push rows to Google Sheets or your CRM, and cap spend per run. Click Try for free to open it in Console. Apify's free plan includes $5 of monthly credit, which buys about 3,000 comments.

See a real run in 47 seconds:

LinkedIn Post Comments Scraper demo video, 47 seconds

▶️ Watch the 47-second demo (MP4, 23 MB, opens in your browser) · Transcript

What can LinkedIn Post Comments Scraper do?

  • 💬 Scrape comments and replies from any public LinkedIn post, no cookies needed
  • 👍 Pull everyone who reacted (like, celebrate, love, insightful, support, funny, curious), filterable by type
  • 👤 Return name, headline, profile URL, profile id and person/company type for every commenter and reactor
  • 📊 Give each comment its reaction breakdown, reply count, thread rank and engagement score
  • 🏷️ Flag the post author's own comments and measure hours between post and comment
  • 🔎 Filter by keyword, minimum reactions, recency window, or drop the author's replies
  • 🧹 One row per person mode for a clean lead list across many posts
  • 💸 Pay per row. Rows removed by a filter are never billed

What data can you extract from LinkedIn comments?

Every comment or reply row carries 49 fields. The ones people use most:

FieldDescription
itemTypecomment, reply or reaction
textFull comment text
commentUrlDirect link to the comment on LinkedIn
createdAtWhen it was posted (ISO 8601, UTC)
personName, personHeadline, personUrlWho wrote or reacted, with their headline and profile link
personProfileIdStable LinkedIn id. Use it to match people across posts
personTypeperson or company (company pages comment and react too)
isPostAuthortrue when the comment is by the account that published the post
isReply, parentCommentId, parentCommenterNameThread position
totalReactions, reactionLike ... reactionCuriousHow the comment itself was received
replyCount, engagement, rankReply count, reactions plus replies, and order in the thread
hoursAfterPostHours between the post and the comment
isQuestion, hasUrl, urls, hashtags, wordCountText signals for sorting and filtering
reactionTypeOn reaction rows: like, celebrate, love, insightful, support, funny or curious
postUrl, postAuthorName, postPostedAt, postCommentsTotalThe post each row belongs to

The Console People view lists commenters and reactors side by side; Top comments sorts the thread by engagement.

How to scrape LinkedIn post comments

  1. Click Try for free to open the Actor in Apify Console.
  2. Paste your LinkedIn post URLs. Any post link works: the /posts/... link from the share button, a /feed/update/urn:li:activity:... link, or the bare activity id.
  3. Set Max comments per post. 50 is enough to see what the data looks like.
  4. Optional: tick Also scrape who reacted and pick the reaction types you care about.
  5. Click Start. Rows stream into the dataset as each post is processed.
  6. Open the Storage tab and export as CSV, Excel or JSON, or fetch the dataset from the API.

No LinkedIn account is involved at any point.

How much does it cost to scrape LinkedIn post comments?

Pricing is per row. There is no charge for compute time.

EventWhen it firesPrice
comment-scrapedEach comment or reply added to your dataset$0.0015
reaction-scrapedEach reaction row added to your dataset$0.0008
post-processedEach post URL processed, even if it returns nothing$0.01

Worked examples

  • 100 comments from 1 post costs $0.16
  • 2,000 comments from 10 posts costs $3.10
  • 5 posts with 100 comments and 500 reactions each costs $2.80

Apify's free plan ($5/month) covers roughly 3,000 comments. Rows removed by keywords, minCommentReactions, postedWithin or dedupePeople are never pushed, so they cost nothing. To cap spend, set maxCommentsPerPost, maxReactionsPerPost and maxDatasetItems; the run stops as soon as a limit is hit.

Input

FieldTypeRequiredDefaultDescription
postUrlsarrayyes—LinkedIn post URLs, urn:li:activity:... URNs or bare ids. Up to 1,000 per run
maxCommentsPerPostintegerno100Comment rows per post, 1 to 5,000. Replies count toward it
includeRepliesbooleannotrueReturn replies as their own rows with parentCommentId
sortOrderstringnomostRelevantmostRelevant (LinkedIn's thread order) or mostRecent (newest first)
postedWithinstringnoanyKeep only comments from the last 24h, week, month, 3months, 6months or year
keywordsarrayno[]Keep only comments containing one of these words or phrases
minCommentReactionsintegerno0Skip comments with fewer reactions than this
excludeAuthorCommentsbooleannofalseDrop comments and replies written by the post's author
includeReactionsbooleannofalseAlso return one row per reaction
maxReactionsPerPostintegerno100Reaction rows per post, 1 to 5,000
reactionTypesarrayno[]Only these reaction types: like, celebrate, love, insightful, support, funny, curious
dedupePeoplebooleannofalseKeep the first row per person across the whole run
maxDatasetItemsintegerno10000Hard cap on rows saved across all posts
{
"postUrls": [
"https://www.linkedin.com/posts/google_welcome-to-the-gemini-era-activity-7196224250288955393-hd08"
],
"maxCommentsPerPost": 50,
"includeReplies": true,
"sortOrder": "mostRelevant",
"includeReactions": true,
"maxReactionsPerPost": 50
}

Which sort order should I pick?

mostRelevant walks the thread the way LinkedIn shows it and is the default. mostRecent lists newest first and pairs with postedWithin: the run stops paging the moment it reaches comments older than the window, so a scheduled "what came in this week" job costs only the new rows.

Output

Each comment, reply or reaction is one dataset item. This is a comment row from the input above:

{
"itemType": "comment",
"commentId": "7197584194053513216",
"commentUrl": "https://www.linkedin.com/feed/update/urn:li:ugcPost:7196223849250627584?commentUrn=urn%3Ali%3Acomment%3A%28ugcPost%3A7196223849250627584%2C7197584194053513216%29",
"text": "Why isn't there any Customer Service with Google? When someone is stealing your ad and reviews, you can not reach anyone by phone nor email.",
"createdAt": "2024-05-18T13:09:56.511000Z",
"createdAtTimestamp": 1716037796511,
"isReply": false,
"parentCommentId": null,
"parentCommenterName": null,
"replyCount": 3,
"isEdited": false,
"isPinned": false,
"rank": 1,
"personName": "Pat M.",
"personHeadline": "Hard Worker with many different skills to share.",
"personUrl": "https://www.linkedin.com/in/pat-m-5314221b6",
"personProfileId": "ACoAADJAgnUBVjObaUWmRKkntr2JIlK5FIQYFa8",
"personUsername": "pat-m-5314221b6",
"personPicture": "https://media.licdn.com/dms/image/v2/.../profile-displayphoto-shrink_800_800/0/1662051050466",
"personType": "person",
"isPostAuthor": false,
"totalReactions": 19,
"reactionLike": 18,
"reactionCelebrate": 0,
"reactionLove": 1,
"reactionInsightful": 0,
"reactionSupport": 0,
"reactionFunny": 0,
"reactionCurious": 0,
"engagement": 22,
"wordCount": 26,
"charCount": 141,
"hashtags": [],
"urls": [],
"hasUrl": false,
"isQuestion": true,
"hoursAfterPost": 90.1,
"reactionType": null,
"postId": "7196224250288955393",
"postUrn": "urn:li:activity:7196224250288955393",
"postUrl": "https://www.linkedin.com/feed/update/urn:li:activity:7196224250288955393/",
"inputUrl": "https://www.linkedin.com/posts/google_welcome-to-the-gemini-era-activity-7196224250288955393-hd08",
"postAuthorName": "Google",
"postAuthorUrl": "https://www.linkedin.com/company/google/",
"postPostedAt": "2024-05-14T19:06:00.650000Z",
"postTotalReactions": 7095,
"postCommentsTotal": 436,
"postRepostsCount": 613,
"scrapedAt": "2026-09-16T10:30:00Z"
}

A reaction row has itemType: "reaction", reactionType, the same person* and post* blocks, and no comment fields.

A run summary is saved to the key-value store as OUTPUT, with per-post counts (commentsTotal on the post versus what was collected). Its message is also shown as the run's status in Console:

{
"status": "SUCCESS",
"reason": null,
"stats": { "comments": 41, "replies": 9, "reactions": 50, "posts_processed": 1, "filtered_out": 0, "items": 100 },
"posts": [
{ "postId": "7196224250288955393", "commentsTotal": 436, "commentsCollected": 41, "repliesCollected": 9, "reactionsCollected": 50, "postAuthorName": "Google", "error": null }
],
"message": "Collected 41 comments, 9 replies and 50 reactions from 1 of 1 post."
}

status is SUCCESS, PARTIAL_SUCCESS (some posts could not be read), NO_RESULTS, STOPPED (the run could not continue, and message says why) or VALIDATION_ERROR (a problem with the input). A post that could not be read carries its reason in posts, and is not charged.

Use cases

Start with one of these six prefilled examples:

API and integrations

Run it from your own code with the Apify API. Swap in your token; the Actor id stays as written.

Python

from apify_client import ApifyClient
client = ApifyClient("<YOUR_API_TOKEN>")
run = client.actor("capable_cauldron/linkedin-post-comments-scraper").call(run_input={
"postUrls": ["https://www.linkedin.com/posts/google_welcome-to-the-gemini-era-activity-7196224250288955393-hd08"],
"maxCommentsPerPost": 100,
"includeReactions": True,
})
for item in client.dataset(run["defaultDatasetId"]).iterate_items():
print(item["itemType"], item["personName"], "-", item.get("text") or item.get("reactionType"))

JavaScript

import { ApifyClient } from "apify-client";
const client = new ApifyClient({ token: "<YOUR_API_TOKEN>" });
const run = await client.actor("capable_cauldron/linkedin-post-comments-scraper").call({
postUrls: ["https://www.linkedin.com/posts/google_welcome-to-the-gemini-era-activity-7196224250288955393-hd08"],
maxCommentsPerPost: 100,
includeReactions: true,
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();

CLI

$apify call capable_cauldron/linkedin-post-comments-scraper --input-file input.json --silent --output-dataset

Connect results to Google Sheets, HubSpot, Airtable, Slack, Make, Zapier or n8n from the Actor's Integrations tab, run it on a Schedule to watch a post over time, or fire a webhook when a run finishes.

FAQ

This Actor collects comments and reactions that are publicly visible on LinkedIn, without logging in. You are responsible for how you use the data, including compliance with LinkedIn's terms and the data-protection laws that apply to you (GDPR, CCPA). If you build outreach lists, respect opt-outs and local rules on unsolicited contact.

Do I need a LinkedIn account or cookies?

No. You paste post links and nothing else. Nothing is done with your LinkedIn account and there is nothing to refresh weekly.

Why did I get fewer comments than I asked for?

Either the post has fewer public comments than maxCommentsPerPost (the run summary shows commentsTotal for the post), a filter removed some (filtered_out in the summary), or maxDatasetItems was reached across all posts. Replies are returned as LinkedIn attaches them to a comment, so very long reply chains can be shorter than replyCount.

Why is isPostAuthor null on some rows?

The author check needs the post's own details. When those cannot be loaded for a post, the flag is null rather than a guess, and hoursAfterPost is null too. Everything else on the row is unaffected.

Can I get only the people who reacted, without comments?

Set maxCommentsPerPost to 1, turn on includeReactions, and set maxReactionsPerPost to the number you need. Pick specific reactionTypes if you only want, say, celebrations.

Can I scrape LinkedIn comments with Python?

Yes. See the Python snippet under API and integrations. The apify-client package is on PyPI; pass the same input you would use in Console.

How do I find the posts to scrape?

Pair this Actor with LinkedIn Profile Posts Scraper. Scrape a profile's posts first, then feed the post_url values into postUrls here. Both run without cookies.

Other Actors by capable_cauldron

ActorWhat it does
App Store Reviews ScraperReviews and ratings for iPhone and iPad apps, grouped by app and country
Company Job Postings ScraperOpen roles and hiring summaries from supported company job boards
Bulk Email ValidatorSyntax, mail-routing, disposable-domain and role-inbox checks
Verified Work Email FinderVerified professional emails from LinkedIn URLs or a name and company domain
GTM Account EnrichmentPublic company contacts, technologies and hiring signals with an account fit score
LinkedIn Profile Posts & Comments ScraperPosts from any LinkedIn profile with up to 50 comments and replies per post, no cookies needed
Investor Database SearchFilter investors by stage, industry and geography and export available partner contacts
LinkedIn Comment ScraperLinkedIn comments and replies using your own session cookies
LinkedIn Profile Posts ScraperPublic profile posts with 56 enriched fields, including engagement and content metadata
Ad Scraper: Meta, Google, LinkedIn & TikTokCompetitor ads from Meta, Google, LinkedIn and TikTok in one dataset
TikTok Shop USA ScraperUS product, shop, creator and shoppable-video data from TikTok Shop
Website Contact ScraperPublic emails, phone numbers and social profile links from company websites
Website Tech Stack DetectorVisible website technologies and the evidence supporting each detection
LinkedIn Post Search ScraperKeyword searches for public LinkedIn posts with text, authors and engagement

Support

Found a bug or need a field that isn't here? Open an issue on the Actor's Issues tab. Issues are usually answered within 24 hours. If you need a custom version (profile enrichment for each commenter, sentiment labels, a private deployment), describe it in an issue and we will scope it.