🏯 Tweet Scraper V2 (Pay Per Result) - X / Twitter Scraper
Pricing
$0.40 / 1,000 tweets
🏯 Tweet Scraper V2 (Pay Per Result) - 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!
3.7 (65)
Pricing
$0.40 / 1,000 tweets
649
Total users
14.7k
Monthly users
1.3k
Runs succeeded
>99%
Issue response
4.6 hours
Last modified
3 hours ago
It is getting far less comment than expected.
Closed
I am trying to scrape all replies under a tweet and it is expected to be 2802. But it is getting around 200 and it changes for each run.
Run ID: Sjz9wHkmf6b3kK51n
blooming_bracelet
I use only conversation id input.
Hey there!
You are hitting Twitter with two different approaches. One with search, one with Conversation ID.
- If you use conversation ID only, you will retrieve the highest-level tweets and possibly less coverage. This is how Twitter UI works. For example, Twitter UI shows the number of replies with all the levels including replies to replies, etc.
- If you use
searchfunctionality, you can get higher coverage with deeper-level tweets. Unfortunately, that's how Twitter and this actor works.
If you want to increase your coverage as much as possible, my suggestion would be to remove everything from the input, using only searchTerms and apply a different version of the following query: conversation_id:XXXX since:YYYYY until:ZZZZZZ.
You can think that this actor is an automated version of Twitter UI. We get what you see. One important note to mention: you cannot get more than a specific number (randomized by Twitter) on a list/pagination. You have to split your search or "stream". What I meant by it is that you cannot retrieve 2.8K tweets from a conversation Id most probably. The best option you can use would be the search.
Cheers
