🏯 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!
Hey, i have been using the actor for a while and with similar usage pattern. Now i see this error. Is there some issue
2024-10-29T19:22:05.731Z ACTOR: Pulling Docker image of build llntW9k5sxSXuczh4 from repository. 2024-10-29T19:22:05.833Z ACTOR: Creating Docker container. 2024-10-29T19:22:06.062Z ACTOR: Starting Docker container. 2024-10-29T19:22:08.198Z INFO System info {"apifyVersion":"3.1.11","apifyClientVersion":"2.8.4","crawleeVersion":"3.5.6","osType":"Linux","nodeVersion":"v18.20.4"} 2024-10-29T19:22:08.205Z ERROR You are being rate limited automatically due to high usage or misuse, such as monitoring activities. Please contact the developer.
Hello,
Seems like our backend flagged you for doing monitoring activities as it is not an allowed use case in our actor https://apify.com/apidojo/tweet-scraper#important-note.
Can you please let us know about your use case in details? If it is private, you can reach our via Discord DM or Email.
Cheers
Hey, we run the actor to fetch user account data. currently what i do i to fetch past tweets via a search url, the from tweet level data extract author item and sub-items. This way i can limit the results to 1 per user, i only need author details to create twitter profile features (e.g. verified, followers, etc)
Hello,
You need to use https://apify.com/apidojo/twitter-user-scraper in order to fetch user details. Fetching a single response each time can also be a reason to get flagged since it is not covering the expense of the run.
Cheers
I see, that sounds great - just tested and user-scraper is the perfect match we need. I will work on dev to integrate over the weekend, can you please unlock the current once meanwhile so we can process users? We have been using the actor for a long time and at scale
Hello,
That's great to hear! Let me know if you need any help integrating that. Unfortunately it is not possible for me to unlock it with your current usecase since you are fetching a single item intentionally and all your runs make negative margin for us. The purpose of this actor is to fetch historical tweets.
I hope this makes it clear.
Cheers
That's not an issue , what's the min number - is it 5 like with user scraper? I need a quick fix before i will switch
Hello,
Yes, you need to fetch at least 5 items. Please refer to the documentation of the actor, there is a very specific example with explanation https://apify.com/apidojo/twitter-user-scraper#important-note.
Cheers
Hey, I have started using the User Profile scraper - great actor btw, exactly what i needed! Love it
I also need to use this one to get post like, retweet etc - can you please remove the limit so i can sue both actors? thanks
Hello,
You are being ratelimitted because you are doing monitoring activities. You are trying to fetch the latest tweet for certain queries and you are doing this very often. These kind of activities are not allowed as stated in the documentation/readme. What is your usecase? Can you please let us know your logic and the reason in details? If it is private, you can reach out via Discord or email.
Cheers
that was discussed earlier in this ticket. The requests were coming from legacy deployed code which i just turned off, we are now using the user profile scraper for that. Going forward we will use this scraper to get tweet level data on likes, retweets, replies etc
hey guys, can you pls confirm if this can be solved? otherwise we will need to use another actor.
Hello,
We just lifted your ratelimit. Please fetch at least ~50 items for each of your query, otherwise it is possible for you to get ratelimitted again automatically.
Cheers
- 1.6k monthly users
- 276 stars
- 99.0% runs succeeded
- 6.1 hours response time
- Created in Nov 2023
- Modified about 23 hours ago