Instagram Post Scraper
Pricing
$2.30 / 1,000 results
Instagram Post Scraper
Scrape Instagram posts. Just add one or more Instagram usernames and get your data in seconds including text, hashtags, mentions, comments, images, URLs, likes, locations, and metadata. Export scraped data, run the scraper via API, schedule and monitor runs or integrate with other tools.
4.5 (31)
Pricing
$2.30 / 1,000 results
335
Monthly users
4.2k
Runs succeeded
>99%
Response time
1.8 days
Last modified
a day ago
id | caption | url | commentsCount | likesCount | firstComment |
|---|---|---|---|---|---|
359***66 | Books allow readers to *** at the link in bio. | https://www.instagram.com/p/DH***C/ | 41 | 9028 | More about books 😍 |
359***88 | Photos by @ingo*** about these pumas at the link in bio. | https://www.instagram.com/p/DH***o/ | 143 | 68801 | ❤️ |
359***22 | Meet the Nat*** their stories at the link in bio. | https://www.instagram.com/p/DH***O/ | 136 | 13385 | Omg!!! ❤️ @dzennypha_ |
The data above is synthetic and does not reflect real-world values. View full dataset
Allow user to skip old pinned posts
Closed
I wanted to follow up on the issue above: https://console.apify.com/actors/nH2AHrwxeTRJoN5hX/issues/Cb1U2J8s7W5Tsk2Ex
If you'd like to maintain the default behavior, can you at least add another input variable to ignore old pinned posts? This would open up the periodic scraping use case for me to use here and keep the old behavior for customers with more ad-hoc jobs. Scraping specific accounts daily is a common use case as evidenced by the other comment on my issue before it was closed and this older issue here: https://console.apify.com/actors/nH2AHrwxeTRJoN5hX/issues/5bQdhfugmlsnVAysO
Filtering on our side is too inefficient for our use case when the accounts we're using post at a frequency of 1x per week (very common). This means each week (7 runs, 0-3 pinned posts) I'll get 1 new post vs. 7-14 copies of the irrelevent pinned posts. Practically this results in the agent stepping into the post-page to scrape and wasting 90% it's compute time on resources that fall outside the date filter in the first place. It's also an easy html tag to grab, and filter at the agent level before it spends the compute to open the post and grab the post details.
nurturing_spray
agree
Hey, that seems reasonable, we will discuss how to do it best (and if possible).
fine_neonate
Thanks! I appreciate it. I'll keep an eye out for updates, would love to use this as part of my project
jurassic_row
I agree with you on this. I hope there's a way to filter out old pinned posts
Hi again,
Deployed as latest build, please use json input value skipPinnedPosts": true as in sample run https://console.apify.com/view/runs/Nn2hNCaomBG7hmix0
I'm going to close this issue for now, but if there's still anything unclear, please, let us know. We appreciate customer feedback!
Pricing
Pricing model
Pay per resultThis 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.
Price per 1,000 items
$2.30
