🏯 Tweet Scraper V2 ($0.4 / 1K tweets) - X / Twitter Scraper
Pricing
from $0.40 / 1,000 tweets
🏯 Tweet Scraper V2 ($0.4 / 1K tweets) - X / Twitter Scraper
⚡️ Lightning-fast search, URL, list, and profile scraping, with customizable filters. At $0.40 per 1000 tweets, and 30-80 tweets per second, it is ideal for researchers, entrepreneurs, and businesses! Get comprehensive insights from Twitter (X) now!
2.4 (74)
Pricing
from $0.40 / 1,000 tweets
728
Total users
17K
Monthly users
2.2K
Runs succeeded
>99%
Issues response
5.3 hours
Last modified
an hour ago
The maxItems limit is applied to the entire job
Closed
I need to fetch tweets/retweets/replies/quotes from multiple users using the startUrls and need to apply a limit individually to each profile (while sorting by recency, ideally giving a start date but i guess that isn't possible). But seems there is no way to do this
pksd
I understand this isn't a issue. But didn't find anything regarding this in the docs
Tried this https://apify.com/apidojo/tweet-scraper#fetching-the-tweets-of-a-profile But it only fetches tweets and not the retweets/quotes/replies
Hey there,
The limit is applied to the entire run. If you want to have separate limits, you need to initiate separate runs.
Cheers!
Also for your other question, have you checked the documentation we shard on the readme https://github.com/igorbrigadir/twitter-advanced-search ? You can apply several filters including include:nativeretweet to improve your search
pksd
Hey I did check it out. But this wouldn't return quotes and replies right?
Also is there any way to combine startUrls and filtering based on start-end dates (instead of using maxItems)
pksd
Hey I did check it out. But this wouldn't return quotes and replies right?
Also is there any way to combine startUrls and filtering based on start-end dates (instead of using maxItems)
pksd
My bad by using include:nativeretweets, we get everything
nihir
Any chance you'd be able to support limits per profile? Not sure how your scraper works on the backend, but would have thought that reducing the number of requests the client makes would reduce overhead from spinning up new instances
Hello,
Unfortunately we don't support that. The workaround is to create a run for each of the profile if you want to use mxItems feature.
Cheers!
