Twitter Search API

GetXAPI charges $0.001 per call to the advanced_search endpoint, and each call returns about 20 tweets, so searching 1,000 tweets costs roughly $0.05. There is no subscription and no minimum. The official X API search starts at $5 per 1,000 reads behind a $200 per month floor, so GetXAPI is the cheapest managed path to search tweets at volume. You start with $0.10 in free credits, no card required.

You do not need an X developer account or the official OAuth flow. You do need a GetXAPI key, which is a single Bearer token you copy after a 30-second signup. That key authenticates every search request. There is no app review, no per-endpoint approval, and no waiting period, so you can run your first query in under a minute.

No fixed per-minute or per-day rate limit caps the search endpoint. You pay per call at $0.001, so cost scales with usage rather than a tier ceiling. That makes it practical to run scheduled firehose pulls or backfill a date range without hitting the throttles that gate the official X API search tiers.

Each response includes a cursor token. Pass that token back in the cursor parameter on your next request to fetch the following page, and repeat until the cursor comes back empty. This lets you walk a full result set for a query or a date window without holding state on the server side.

Yes. Set product to Latest and the advanced_search endpoint returns a reverse-chronological feed with tweets that are seconds old, which is what you want for live monitoring and alerting. Set product to Top and you get the most-engaged tweets that match your query instead. Both run against the live X index, not a stale cache.

Yes. The q parameter accepts the same operators you type into X advanced search: from:, to:, filter:verified, min_faves:, min_retweets:, since:, until:, lang:, and geocode:. You can combine them in a single query, for example from:elonmusk min_faves:500 since:2026-01-01. For the full operator reference and combination recipes, read the Twitter advanced search operators guide.

The product parameter controls ranking. Latest returns matching tweets in reverse-chronological order, newest first, which suits real-time monitoring. Top returns the same matches ranked by engagement, highest first, which suits sentiment digests and highlight feeds. Latest is the default if you omit the parameter.

The search API is the query endpoint: you hand it operators and it returns matching tweets. A broad Twitter scraper pulls whole timelines, followers, profiles, and media on top of search. Both run on the same Bearer key and the same flat $0.001 per call. If you only need to search by query, this endpoint is the focused path; if you need full account data, the Twitter scraper covers the wider surface.