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.4 (30)
Pricing
$2.30 / 1,000 results
309
Monthly users
2.8k
Runs succeeded
>99%
Response time
19 hours
Last modified
an hour 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
Issues with Apify Instagram Scraper – Request for Assistance
Hello Support Team,
I am writing to request assistance regarding persistent issues with the Apify/instagram-post-scraper actor. Despite implementing several recommended measures, my requests to Instagram are still being blocked. Below are some details of my configuration and the challenges I am facing:
• I am using a realistic user-agent string to mimic a common browser environment. • Proxy settings are configured by enabling Apify’s proxy service. • I’ve limited the number of concurrent requests using the "maxRequestsPerCrawl" parameter to reduce the load. • For authentication, I am providing the necessary login cookies (including parameters such as csrftoken, sessionid, ds_user_id, etc.) via the "loginCookies" parameter.
Despite these measures, I continue to encounter errors such as “Request got blocked” or receive empty results, even for public profiles. This frequently disrupts the data scraping process and impacts my operations.
Could you please advise if:
There are additional configuration adjustments or parameters that could be fine-tuned to prevent these blocks? Specific best practices or known issues might be contributing to this behavior with the current setup? There is any updated guidance related to handling authentication or IP rotation that I might have overlooked? Any insights or recommendations would be greatly appreciated as I am keen to resolve this issue and ensure stable data retrieval from Instagram.
Thank you very much for your support.
Erik Funder Carstensen (weuts)
Hi 😊
We had issues with the scraper over the last ~24 hours because Meta made changes to some APIs - they should be resolved now 😌.
For the rest of your comment, this scraper does not take parameters like the ones your are referencing - we don't do login, and we handle user-agent, proxy settings and run concurrency internally 😅.
I'll close this issue for now, but if you have further issues with (or questions about) the scraper, feel free to reach out again 😌.
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
