Tweet Scraper|$0.25/1K Tweets | Pay-Per Result | No Rate Limits avatar
Tweet Scraper|$0.25/1K Tweets | Pay-Per Result | No Rate Limits

Pricing

$0.25 / 1,000 tweets

Go to Store
Tweet Scraper|$0.25/1K Tweets | Pay-Per Result | No Rate Limits

Tweet Scraper|$0.25/1K Tweets | Pay-Per Result | No Rate Limits

Developed by

twlo low

twlo low

Maintained by Community

Only $0.25/1000 tweets for Twitter scraping, 100% reliability, swift data retrieval.This incredible low price is almost too good to be true.Thanks to our large-scale operations and efficient servers, we can offer you rock-bottom prices that no competitors can match. Don't miss this opportunity !

4.2 (18)

Pricing

$0.25 / 1,000 tweets

189

Total users

3.6K

Monthly users

1.1K

Runs succeeded

>99%

Issues response

4.2 hours

Last modified

2 days ago

TO

I'm just getting mock data

Open

Tomoro opened this issue
a day ago

"From KaitoEasyAPI, a reminder:Our API pricing is based on the volume of data returned. However, to ensure we can cover our costs on the Apify platform, we have a minimum charge of $X per API call,even if the response contains no results.Thus, we returned N pieces of mock data. We will monitor and adjust the size of N based on the infrastructure costs incurred by Apify.This helps offset the infrastructure costs we incur for each API request, regardless of the data returned. We want to be upfront about this policy so you understand the pricing structure when using our service.Despite adding mock data when no results are found, we're still barely breaking even. Our prices are already very reasonable, but we're committed to maintaining this service to support the growth of your project.Please let us know if you have any other questions!"

KaitoEasyApi avatar

Please provide your runID.

KaitoEasyApi avatar

Please reopen this issue once u have more infomation.

TO

Tomoro

9 hours ago

Vx87wPYUMNgpZYyy6

KaitoEasyApi avatar

Your search criteria returned no results. You can test with the link below.

https://x.com/search?q=(%5C%22Ideal%20boiler%5C%22%20OR%20%5C%22Ideal%20boiler%5C%22)%20(problem%20OR%20fault%20OR%20issue%20OR%20repair%20OR%20breakdown%20OR%20leak%20OR%20pressure%20OR%20noisy%20OR%20E1%20OR%20L2%20OR%20F2)%20-job%20-hiring%20near%3AUK&src=typed_query&f=live

Additionally, there's another issue with your request parameters. If you use the 'searchTerms' field in the request, please include all query conditions within each element of 'searchTerms'.

"searchTerms": [ "from:x since: 2025-07-15_00:00:00_UTC", "from:x11 since: 2025-07-15_00:00:00_UTC" ],