🏯 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.9 (54)
Pricing
$0.40 / 1,000 tweets
631
Monthly users
1.3k
Runs succeeded
>99%
Response time
4.5 hours
Last modified
3 hours ago
Date filters not being respected
Closed
Since roughly ~20th of July our run results and subsequently bill has exploded. This is because the date filters aren't being respected. Looking at past open issues it seems that the input structure has changed. Is it possible to clarify in the run attached got what the input structure should look like to accomplish the behaviour we're after?
Hello,
The input structure hasn't changed however seems like you are using the INPUT in a wrong way. You are providing your query to the author parameter. You need to use searchTerms if you want to use Twitter queries. Please refer to the readme of our actor to get more information on how to use Twitter queries.
https://apify.com/apidojo/tweet-scraper#fetching-the-tweets-of-a-profile
Let me know if this helps.
Cheers
apos_t
Thanks for the quick response.
Can you please confirm whether the input on run szTzskcWnrGeV0yhO is structured in a correct way?
Best,
Hey there,
There is a slight issue. You need to combine these queries together into a single one. Right now, you have 3 different queries.
Something like this:
"from... OR ... since:2024-08-19 until:2024-08-23",
Does that make sense?
Best
apos_t
I tried that with run cfLyS6y1sFyefoK4Y however there it produces more rows than necessary and again out of scope. Should it maybe be on query per author like:
1"from:xyz since:2024-08-19 until:2024-08-23", 2"from:abc since:2024-08-19 until:2024-08-23",
apos_t
Hey there, can you confirm whether the input for run UFvsiN2G60l6WhZOe is correct. Would you make any adjustments to it?
Hello,
It seems correct. Do you have any issues with it?
Cheers
apos_t
Not anymore - the runs appear to have stabilised and the results are closer to the expected range.
Pricing
Pricing model
Pay per resultThis Actor is paid per result. You are not charged for the Apify platform usage, but only a fixed price for each dataset of 1,000 items in the Actor outputs.
Price per 1,000 items
$0.40
