Tweet Scraper|$0.25/1K Tweets | Pay-Per Result | No Rate Limits
Pricing
$0.25 / 1,000 tweets
Tweet Scraper|$0.25/1K Tweets | Pay-Per Result | No Rate Limits
Only $0.25/1000 tweets for Twitter scraping, 100% reliability, swift data retrieval.This incredible low price is almost too good to be true.Thanks to our large-scale operations and efficient servers, we can offer you rock-bottom prices that no competitors can match. Don't miss this opportunity !
4.3 (15)
Pricing
$0.25 / 1,000 tweets
144
Total users
2.5k
Monthly users
892
Runs succeeded
>99%
Issues response
2.9 hours
Last modified
3 days ago
Possible Duplicate tweets and getting charged for them
Closed
RUN id - bG75s8FhhHsgyE22W and DHmuAylvwCx9J4kuV
input search term count - 3,276 Expected tweet count - around 30-40 thousand expected price - around 10$
(Expected numbers are based on previous runs )
Details of run bG75s8FhhHsgyE22W Crawled tweet count - around 90 thousand price - 22.5 $
when i filter unique tweets, tweet count comes down to around 35 thousand. I checked for duplicates in my input search terms - found 3 duplicates - which should not cause this much of a spike. Checked logs - didnt see anything getting queried a lot of times. ( Not sure about this )
Could you please check why this is happening for the 2 run ids ? I have tried to check everything from my end and i dont see any duplicate queries as i mentioned. Not sure if its something else.
Please look into this as soon as possible - Thank you.
Hi. Thank you for your feedback. We will start to investigate this issue.
Beat regards.
Hi, you're absolutely right—there does appear to be a duplicate data issue. However, when I tried to reproduce it myself, I couldn't replicate the problem, and the logs didn't show any anomalies either. That said, the responsibility is on our end.
Here’s how we’ll make it right:
I’ll issue a refund for the duplicate charges, either via cryptocurrency or bank transfer (whichever you prefer).
We’ll also continue monitoring this closely to prevent recurrence.
Let me know your preferred refund method, and I’ll process it right away. Appreciate your patience and for bringing this to our attention!
Best regards.
datapowa1
Thanks for the kind gesture and quick response. We’re currently tied up with a few things, Will get back to you after discussing with our team. So feel free to close the ticket for now. If the issue recurs in our next run, I’ll reopen it. Appreciate your support!
Sure. Thank you so much for your understanding. Wishing you a wonderful day!
datapowa1
Hi, Could you please check this run id : f2ZxcwkZ2Z6EhdqyO. Im suspecting the same issue happened again. Thanks.
Get it. We will check it.
Sorry, we still haven’t been able to identify the issue—our logs don’t show any anomalies. I apologize for the inconvenience this has caused.
If it works for you, I’d recommend switching to our standalone service, which avoids this problem entirely and is also more affordable: $0.15 per 1 000 tweets. The only difference is that you’ll need to handle pagination on your side, because the new service is designed for high performance (each call completes in about 700 ms).
Below is a quick code sample to get you started:
https://twitterapi.io/blog/how-to-monitor-twitter-accounts-for-new-tweets-in-real-time
datapowa1
Actually we have set up everything using Apify and this is easier for us to handle. Could this be something from Apify's end ?
Sorry, I thought I had replied to you. Yes, it's possible that there is a problem with Apify. I have contacted them, but we haven't found out the cause yet.
Hi. If you still have questions, please create an Issue again. Best regards.
