Instagram Post Scraper avatar
Instagram Post Scraper

Pricing

from $1.60 / 1,000 posts

Go to Store
Instagram Post Scraper

Instagram Post Scraper

Developed by

Apify

Apify

Maintained by Apify

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 (33)

Pricing

from $1.60 / 1,000 posts

483

Total users

45K

Monthly users

5.4K

Runs succeeded

>99%

Issues response

2.5 days

Last modified

13 hours 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

CH

Not getting in date sequence data

Closed

chintanbhavsar opened this issue
a month ago

Hi Team,

I recently used the actor to scrape Instagram user posts. However, I noticed that the posts were returned in a random order, not sorted by timestamp. I was expecting the results to be in chronological order — specifically, the latest 25 posts based on their posting time.

Could you please explain the sequence in which the data is returned?

Thanks, Vivek Gupta

alexey avatar

Hi!

The actor scraping posts with the concurrency from 10 to 50 (depending on RAM). As soon as each post is scraped, details are saved to the dataset. That's why the original chronological order is not precise. Posts are scraped in batches on each scroll. Inside the batch, ordering is randomized based on data response time for each post. However total amount of posts by date range or results limit should always be correct.

I will close the issue now, but if there is anything else we can help with, please let us know.