🏯 Twitter (X) User Scraper (Pay Per Result) avatar
🏯 Twitter (X) User Scraper (Pay Per Result)
Try for free

Pay $0.30 for 1,000 users

View all Actors
🏯 Twitter (X) User Scraper (Pay Per Result)

🏯 Twitter (X) User Scraper (Pay Per Result)

apidojo/twitter-user-scraper
Try for free

Pay $0.30 for 1,000 users

Introducing Twitter (X) User Scraper, the ultimate solution for direct user extraction from Twitter (X). It offers blazing speed and comprehensiveness, delivering lightning-fast user extraction features.

CH

Pagination Support

Closed

chkhikvadze opened this issue
a month ago

We have been using it for almost a week to fetch followers and followings of users for our product. However, we are encountering an issue with the scraper actor, as it does not support any kind of pagination. This becomes problematic when we want to retrieve a large number of users, say 100,000 followers, and want to fetch them 100 by 100 with pagination. Fetching 100,000 users in one request can take a long time, and we want to improve the efficiency and usability of our application. Currently, we can only assign one field, maxItems, which is very limited. Each time we call to fetch 100 users, it retrieves the last 100 users, and then we're stuck and cannot perform any further actions. Do you have any suggestions or a workaround to add pagination support?

apidojo avatar

Hey there,

We've received your email as well but since you also opened an issue, I will continue the conversation from here. I've forwarded your question to our engineering team to see if they have a suggestion or workaround for this. Otherwise, I will add this to our feature board and let you know when we implement it. I will let you know when I get some news from our engineers.

Cheers!

apidojo avatar

Hey there,

I just got a response from my team. Unfortunately adding a pagination support to the scraper is technically not possible. Sorry for the inconvenience.

Best!

Developer
Maintained by Community
Actor metrics
  • 259 monthly users
  • 18 stars
  • 99.6% runs succeeded
  • 3.6 hours response time
  • Created in Nov 2023
  • Modified about 22 hours ago