
Twitter (X.com) Scraper Unlimited ($0.0004 / tweet): No Limits
Pricing
Pay per event

Twitter (X.com) Scraper Unlimited ($0.0004 / tweet): No Limits
Introducing Twitter Scraper Unlimited, the most comprehensive Twitter data extraction solution available. Our enterprise-grade scraper offers unmatched capabilities with a transparent event-based pricing model, making it perfect for both small-scale and large-scale data extraction needs.
3.1 (24)
Pricing
Pay per event
236
Total users
7.9K
Monthly users
2.3K
Runs succeeded
>99%
Issues response
7.2 hours
Last modified
a day ago
Inconsistent Column Values Returned by Crawler
Closed
Hello, Crawling the same post URL once a day, but the column values returned differ with each attempt, making automation difficult.
Request 1: https://console.apify.com/view/runs/yiaTt2OhCBeSUcdJw Request 2: https://console.apify.com/view/runs/yUPdxw9y9pho1kc8u
Although both requests use the same input URL, the number and names of the returned columns differ. Please look into this issue.

Hello,
Have you checked the raw response? The returned value is identical besides isVerified
and location
variables of the author. You can use a diff tool (like https://jsondiff.com/) to verify this, I am attaching a very zoomed out screenshot to show you both together.
The reason of the difference for these 2 fields is purely related to Twitter as sometimes it doesn't return them.
Can you please elaborate on which values look different and make your automation difficult?
Cheers
brisk_zest
Hello,
The differences I mentioned mainly occur in the author field, particularly in columns like isVerified and location, as you pointed out. The issue is that the data returned in this field is not consistent.
I crawl the same URL every day, but today the canDm and canMediaTag fields are missing. (Reference: https://console.apify.com/view/runs/Sdi1NvbsHnekRYR93)
Is it inherently random which fields are returned and which are omitted, depending on Twitter’s response behavior?

Hello again,
Thanks a lot for the example. As mentioned, we are using the exact same logic each time you scrape a URL and don't have any custom filters. We directly provide you the raw response we get from Twitter.
I will redirect this to our engineering team to have a second look.
Cheers