🏯 Tweet Scraper V2 ($0.4 / 1K tweets) - X / Twitter Scraper avatar
🏯 Tweet Scraper V2 ($0.4 / 1K tweets) - X / Twitter Scraper

Pricing

from $0.40 / 1,000 tweets

Go to Store
🏯 Tweet Scraper V2 ($0.4 / 1K tweets) - X / Twitter Scraper

🏯 Tweet Scraper V2 ($0.4 / 1K tweets) - X / Twitter Scraper

Developed by

API Dojo

API Dojo

Maintained by Community

⚡️ 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!

2.6 (72)

Pricing

from $0.40 / 1,000 tweets

719

Total users

17K

Monthly users

2.1K

Runs succeeded

>99%

Issues response

5.3 hours

Last modified

13 hours ago

YO

Date bias while scraping

Closed

yoy48kes opened this issue
10 days ago

Hi,

I did several test runs and I always have the same problem

I need to scrape tweets using dates (im using 4 months windows per run)

However regardless of how many tweets i scrape they are all condensed in a few dates, usually the last day of the month. How can I solve this?

For example if I have to scrape 3k tweets from 01.01 to 30.04, most of the tweets are all on the date 29.04 (so the data is biased towards the end of the time window)

apidojo avatar

Hello,

Since they are returned by date, there is nothing much to do about this besides adjusting your queries.

Our actor uses your twitter query on twitter and returns you whatever it can get from it. You can get more information on https://developer.x.com/en/docs/x-api/v1/rules-and-filtering/search-operators

Cheers

YO

yoy48kes

10 days ago

Sorry but how can this be? What’s the point of since and until then?

I did another run where i only used one word for my interval and still ALL the resuls were on one single date, and it’s always the last day that I put for my interval

For example if i search from 01.12.2020 to 31.12.2020, every single result is on the 31 december

apidojo avatar

Hello,

This is how twitter queries are working and it is developed by Twitter, not by us. If you are using sort: Latest, these queries return the tweets sorted by date and if there are lots of tweets and you set maxItems, you can only get the first ones.

Please refer to the Twitter documentation to learn more on how these queries work. Our scraper is using exactly what you provide to it and return you the data. You can also test your queries on Twitter web UI before using them on the scraper. Please refer to the screenshot I attached.

Cheers