🏯 Instagram Scraper (Pay Per Result)
Pricing
$0.50 / 1,000 posts
🏯 Instagram Scraper (Pay Per Result)
Famous for its blazing-fast speed and completeness, it offers rapid and efficient scraping of many URLs such as; location, audio, tag, and profile. It's incredibly cost-effective at only $0.50 for every 1000 posts, capable of scraping 100-200 posts each second!
4.9 (23)
Pricing
$0.50 / 1,000 posts
99
Total users
2.3K
Monthly users
346
Runs succeeded
>99%
Issues response
2.7 hours
Last modified
5 days ago
Actor stops after 757 results - ERROR C009: Could not get posts for audio ID
Closed
Hi,
I'm experiencing an issue where the Instagram Audio Scraper actor stops prematurely when trying to scrape reels from an Instagram Audio URL.
Expected behavior: I need to scrape between 50,000-75,000 reels from an Instagram Audio URL.
Actual behavior: The actor stops after retrieving only 757 results.
Error message: The run log shows the following error: "ERROR C009. Could not get posts for audio ID: 191281873793422"
Steps to reproduce:
- Run the actor with an Instagram Audio URL
- The actor begins scraping successfully
- After 757 results, it encounters the error and stops
Additional context:
- I'm on the Starter plan specifically to use this actor for larger scraping tasks
- The actor worked fine for the initial results but seems unable to continue past this point
I'd appreciate any help in resolving this issue so the actor can handle larger volumes of data as intended. Please let me know if you need any additional information to investigate this problem.
Could you please provide an assessment of whether this issue can be fixed and an estimated timeframe for the fix? If it's not possible to resolve this issue or if it would take too long to implement a solution, I would need to request a refund from Apify support as the actor doesn't meet my requirements for large-scale data collection.
Thank you!
Hello,
This is expected behavior when using a scraper. Since our scraper navigates Instagram page by page, Instagram can sometimes prematurely end pagination, which prevents the actor from retrieving additional data.
The scraper does its best to fetch posts and reels, but as mentioned, it’s not an API, so there are inherent limitations. This behavior is also very non-deterministic. For example, I ran the actor again with the same input, and this time it was able to fetch a bit more posts (~850).
If you’re looking for a refund, please note that we are not affiliated with Apify directly. We’re only the developers of this scraper and cannot issue refunds for your Apify plan. For any billing-related issues, please contact Apify support directly.
Cheers
