Search X (Twitter) Posts by Keyword
Export X (Twitter) posts for any search term with likes, reposts, replies, views, post date and author handle. Example: AI agents. No login needed.
Input
Output fields
Sign up on Apify or log in
The X (Twitter) Scraper - Tweets, Search & Profiles | No Login Actor is ready to run with the inputs already set for "Search X (Twitter) Posts by Keyword". Sign up or log in and you'll land in Apify Console with a copy of this exact task.
Start the "Search X (Twitter) Posts by Keyword" task
The X (Twitter) Scraper - Tweets, Search & Profiles | No Login Actor will start running based on the input automatically. You can also change all the input fields, like search terms (search mode) and max results, to match your specific use case.
Receive the "Search X (Twitter) Posts by Keyword" output
Monitor the progress in real time. You will be notified as soon as your dataset is complete and ready for review. Each result includes data such as tweetid, text, createdat, and more.
Integrate into your workflow
The final output is delivered in JSON, CSV, or Excel format, ready to be plugged into your workflow. You can also run the "Search X (Twitter) Posts by Keyword" task via API.

Export X (Twitter) posts for any search term with likes, reposts, replies, views, post date and author handle. Example: AI agents. No login needed.
No. The task reads public X (Twitter) data, so you don't need an account, cookies or your own proxies. Open the task and click Start.
Change “Search terms (search mode)” in the input above and start the run. The other settings can stay as they are.
Up to the “Max results” value: this example asks for 50. It is the total for the whole run, so a run never returns more than you asked for.
You pay per result, with no monthly rental. The current price per 1,000 results is on the Actor's Pricing tab, and Apify shows what each run cost when it finishes.
Yes. Save the task to your account and add a schedule in Apify Console (hourly, daily or weekly). Download results as JSON, CSV or Excel, or read them through the Apify API and integrations.
Every run fetches the data from X (Twitter) at the moment it runs, so counts such as likes, views or prices are current as of that run.