🏯 Tweet Scraper V2 (Pay Per Result) - X / Twitter Scraper
Pay $0.40 for 1,000 tweets
🏯 Tweet Scraper V2 (Pay Per Result) - X / Twitter Scraper
Pay $0.40 for 1,000 tweets
⚡️ Lightning-fast search, URL, list, and profile scraping, with customizable filters. At $0.30 per 1000 tweets, and 30-80 tweets per second, it is ideal for researchers, entrepreneurs, and businesses! Get comprehensive insights from Twitter (X) now!
Please contact the developer.
Closed
2024-11-21T07:11:24.206Z ERROR You are being rate limited automatically due to high usage or misuse, such as monitoring activities. Please contact the developer.
INp3EhZcWZ1ilIZvH
Hello,
There might be several reasons for this:
- You are doing too many runs. You can have max 1 run concurrently (max 10 queries batched)
- You are getting less items. You need to fetch at least 50 tweets per query
- You are conducting monitoring activities. Monitoring activities are not allowed as stated in the documentation https://apify.com/apidojo/tweet-scraper#important-note. The main purpose of the actor is to fetch historical data, not monitor tweets on hashtags/profiles/specific queries etc within a timeframe.
I think in your case, you are not fetching at least 50 query per run. When I check your runs, I see that some of your queries even return 0 results like:
https://console.apify.com/view/runs/Rn3rOak3sZK6LFpcI
If you are not conducting monitoring activities why is this the case? Can you let us know about your usecase and why you are using zero-result queries?
If you think you are not doing any of these, please reach out via Discord or email with your usecase and we can talk about lifting the ratelimit.
Cheers
Cheers
Hi API Dojo Team,
Thank you for your feedback and for pointing out potential issues. Let me clarify our use case to ensure it aligns with your guidelines.
-
Historical Search, Not Monitoring We are not conducting monitoring activities. Our focus is entirely on historical data. We perform daily searches for historical posts, but these are not tied to specific profiles or very short timeframes. Instead, we use keywords over time to gather insights.
-
Zero-Result Queries Occasionally, our searches may return zero results. This happens because we look for keywords without knowing how often they are mentioned. For instance, we anticipate discussions around a term “ice cream", but if no one mentions “ice cream", we still log those attempts. We aim to remain within your search parameters while capturing meaningful data, how would you recommend we tackle this?
-
Geographic Context We also run keyword searches restricted to specific geographic locations. For example, a term like "munchkins" might be commonly used globally, but we focus on how it’s used within Australia. To manage this, we currently run two separate scripts simultaneously. However, we can run them consecutively if that better suits your system requirements.
Could you confirm if this addresses the concerns outlined in your email? We’re happy to modify our approach further if necessary to ensure compliance.
Thank you for your guidance and support.
REM
Hello,
Actually all these cases fall under monitoring.
- When you look for a keyword without knowing if there are any tweets there, you are actually monitoring that keyword.
- Same goes for geo filters. When you are checking if there are any specific tweets in a geographic location, you are actually monitoring that location for specific tweets.
The main reason behind this prohibition is to prevent these low numbered queries. When you monitor, it is impossible to know beforehand and there is a high possibility of getting less than 50 tweets.
If you can come up with an alternative usage and can guarantee minimum 50 tweets per query, please reach out via Discord or email and we can talk about lifting the ratelimit.
Cheers
API DojoActor Metrics
1.6k monthly users
-
306 stars
99% runs succeeded
4.3 hours response time
Created in Nov 2023
Modified 18 hours ago
