🏯 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.0 (66)
Pricing
$0.40 / 1,000 tweets
682
Total users
16K
Monthly users
1.9K
Runs succeeded
>99%
Issues response
5 hours
Last modified
12 hours ago
rate limited
Closed
run id: SQnXWSnmP9NvZgAE9 I am collecting a single user's tweets during one year. It is not monitoring activity (because I am collecting tweets from a set period in past) and it must be collecting a lot of tweets. So why is my search getting the "rate limited" error?
Hello,
You are getting rate-limited by our actor which you can see in the Logs. 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 it the 2nd one. When I check your history, I see that your average is 7 tweets per query but you need to fetch at least 50 per query. Also fetching a single user's tweet falls under monitoring.
Can you please let us know about your use-case in detail? How are you fetching this information (development logic) and why are you doing it (usecase/product)? Also do you think you can guarantee to fetch min 50 per query?
If your answers are private, you can also reach out via Discord or email.
Cheers
gold_junco
I resolved the issue in another way. But what I was doing was that I have previously collected tweets addressed to a list of users. I want to do a sentiment analysis of these tweets. But to do that it seemed that I need also the original post of the user to which the response I am analysing was addressed. So I was using the inReplyToId to go to the particular page and fetch the replies and ended up being rate limited. Eventually I resolved this by other means: I had previously scraped all tweets of the same list of users and I was able to match these two tables. However, I discovered that one user was missing from my original list and I would need to fetch both the user's own tweets as well as the replies to these tweets. It seems that it would also fall under the monitoring. Should I just run a query for 10 users to avoid this?
Hello,
If you are going to batch those 10 users into a single query like (from:xx OR from:yy), it might work, however if you are going to batch them with separate queries, you need to fetch 50 for each of them.
Also fetching a single tweet is highly prohibited, you should avoid doing it at all.
Please reach out via Discord or email to talk further about this.
Cheers
