LinkedIn Profile Posts Bulk Scraper (No Cookies)⚡$2 per 1k avatar
LinkedIn Profile Posts Bulk Scraper (No Cookies)⚡$2 per 1k

Pricing

$2.00 / 1,000 posts

Go to Store
LinkedIn Profile Posts Bulk Scraper (No Cookies)⚡$2 per 1k

LinkedIn Profile Posts Bulk Scraper (No Cookies)⚡$2 per 1k

Developed by

HarvestAPI

HarvestAPI

Maintained by Community

Extract posts from LinkedIn profiles including content, media, engagement, reactions, comments and more. No cookies or account required. Concurrency + fast response times make mass scraping fast ⚡

4.0 (3)

Pricing

$2.00 / 1,000 posts

50

Total users

778

Monthly users

539

Runs succeeded

>99%

Issues response

8.6 hours

Last modified

8 hours ago

JC

Add post likers & commenters' profile URLs when "Scrape additional information" is enabled

Closed

jacob.cooper opened this issue
2 months ago

If the "Scrape additional information" toggle is turned on, could the actor also return: The profile URLs of users who liked each post The profile URLs of users who commented on the post Many other LinkedIn scrapers include this data, and it would be super helpful for engagement analysis and outreach purposes. Let me know if this is feasible

HarvestAPI avatar

I was thinking of making it as a separate Actor, I see it's common for [no cookies] solutions. There could be 1000s of likes, comments, etc. per post. That's a lot more load to scrape while we charge per post result in this actor. Or we could push user engagements into results as well, so it will be possible to map it by postId. Another option would be to create a new actor that charges per event, and charges less for scraping engagements, that could output user engagements nested in posts. What option would work for you?

JI

jsqd2.ia

2 months ago

the number of like stay at 0...

HarvestAPI avatar

It should scrape the total number of likes. Maybe that's a repost? Please provide a link

HarvestAPI avatar

We just added the reactions and comments scraper! You can enable it in this actor's input, and it will scrape and push them into results (disabled by default). It will also push them into their appropriate parent post record.

Each record now has type property that specifies if it's a post, reaction or comment.