Linkedin Post Scraper ✅ No cookies ✅ $2 per 1k posts
Pricing
Pay per event
Linkedin Post Scraper ✅ No cookies ✅ $2 per 1k posts
Scrape unlimited Linkedin posts without risking your Linkedin account. Live data, Super fast scraping at affordable cost. High success rate
3.9 (4)
Pricing
Pay per event
32
Monthly users
306
Runs succeeded
>99%
Response time
2.4 days
Last modified
14 days ago
Retrieved results do not match with the 'limitPerSource' parameter
When we use the 'limitPerSource' parameter with e.g. 100, we retrieve around 50 posts. With the parameter set to 50 we retrieve 30 posts roughly. The retrieved posts aren't chronologically sorted, which makes analysis difficult. Sometimes there are even posts, from other 'authorType' but flagged with 'isRepost:false' - which doesn't make sense for me. There is some fixing required.
remorrow
Additionally, we've recongized duplicated posts in the dataset retrieved
remorrow
After some more troubleshooting it got clear: The actor pulls always the same 10 posts and repeats those in the result dataset
get_the_deets
I noticed the same issue (the actor only pulls the last 10 posts and then repeats those posts in the data set). Did you find a way to fix this and get it to put more than 10 unique posts?
Hi, Thanks for opening the issue and helping me to make this actor better. Let me check and get back to you
Sent an update, please check and confirm if it is fixed
Pricing
Pricing model
Pay per eventThis Actor is paid per result. You are not charged for the Apify platform usage, but only a fixed price for each dataset of 1,000 items in the Actor outputs.
Cost per actor start per 1GB
$0.005
Flat fee for starting an Actor run for each 1 GB of memory.
Cost per post scraped
$0.002
Cost per post scraped
