Twitter / X Reply Scraper (Apify Actor)

Scrapes Latest search results via X GraphQL SearchTimeline, then loads direct replies per tweet with TweetDetail (same flow as the standalone scraper: dynamic query IDs from main.*.js, x-client-transaction-id from XClientTransaction, controller_data from the first timeline page).

Input

Field	Description
startUrls	Start URLs — X search URLs (q= is parsed as the query). Legacy urls still accepted.
maxSearchResults	Maximum Search Results — max tweets per start URL (default 5).
maxReplies	Maximum Replies — max direct replies stored per tweet (default 5).
authToken / ct0	Session cookies, or env AUTH_TOKEN / CT0.
proxyConfiguration	useApifyProxy: false → direct first, then DC → residential on blocks. true → Apify proxy from the start.

Output (dataset)

Each item: tweetLink, tweetContent, tweetDate, handle, counts, repliesData (nested reply objects).

Run locally

cd Twitter-X-Reply-Scraper
pip install -r requirements.txt
# Set AUTH_TOKEN and CT0, then:
apify run

Data is only from public X content; you are responsible for compliance with X’s terms and applicable law.

What are other Twitter scraping tools?

If you want to scrape specific Twitter data, you can use any of the dedicated scrapers below for faster and more targeted results.

Scraper Name	Scraper Name
Twitter (X) Tweets Scraper	Twitter Profile Phone Number Scraper
Twitter (X.com) Tweets & Profiles Scraper	Twitter Profile Scraper
Twitter B2b Email Scraper	Twitter Trends Scraper
Twitter B2b Lead Scraper	Twitter User Following Scraper
Twitter B2b Phone Number Scraper	Twitter X Posts Scraper
Twitter Email Scraper	X Twitter Email Scraper
Twitter Lead Scraper	X Twitter Lead Scraper
Twitter Phone Number Scraper	X Twitter Phone Number Scraper
Twitter Profile Email Scraper	X Twitter Posts Search
Twitter Profile Lead Scraper