X Twitter Tweet Scraper

Scrape X/Twitter tweets by keyword, advanced search query, search URL, author, date range, engagement threshold, media type, verified-account filter, or collect replies for specific tweet IDs. The Actor returns structured tweet records for brand monitoring, campaign research, market analysis, reporting, and automation workflows.

What this Actor does

• finds tweets by simple keyword phrases or full X/Twitter advanced search queries
• collects tweets from X/Twitter search URLs
• collects replies for specific posts with tweetIds or tweet URLs
• filters by author, reply target, mentioned users, date range, language, hashtags, and exact phrases
• filters by minimum likes, retweets, replies, image posts, video posts, or verified users
• supports latest and top sorting
• paginates results and lets you cap output with maxItems

Common use cases

• monitor brand, product, executive, or competitor mentions
• collect tweets for campaign hashtags and launches
• track high-engagement posts in a market or topic
• build social listening and sentiment-analysis datasets
• collect replies and reactions from a specific post
• export tweet datasets for BI, LLM enrichment, classification, or alerts

Output

The dataset contains matching tweet records with tweet text, URL, timestamp, author details, engagement counters, hashtags, links, media, conversation IDs, and other fields when available.

Example output

{
  "id": 1891042203344556600,
  "id_str": "1891042203344556600",
  "url": "https://x.com/openai/status/1891042203344556600",
  "date": "2026-02-20T08:30:00+00:00",
  "lang": "en",
  "rawContent": "We shipped a new update today.",
  "replyCount": 42,
  "retweetCount": 310,
  "likeCount": 1520,
  "quoteCount": 18,
  "bookmarkedCount": 0,
  "conversationId": 1891042203344556600,
  "conversationIdStr": "1891042203344556600",
  "hashtags": ["AI", "OpenAI"],
  "cashtags": [],
  "mentionedUsers": [],
  "links": [],
  "viewCount": 120034,
  "user": {
    "id": 4398626122,
    "id_str": "4398626122",
    "url": "https://x.com/openai",
    "username": "openai",
    "displayname": "OpenAI",
    "followersCount": 5500000,
    "friendsCount": 12,
    "verified": true
  },
  "media": {
    "photos": [],
    "videos": [],
    "animated": []
  },
  "_type": "snscrape.modules.twitter.Tweet"
}

How to use

1. Open the Actor on Apify.
2. Choose Search tweets for keyword/query collection or Replies for specific tweets for tweet reply collection.
3. For search, enter searchTerms for a simple search, rawQuery for advanced X/Twitter search syntax, or startUrls for search URLs. For replies, enter tweetIds or tweetUrls.
4. Add optional filters such as author, date range, engagement thresholds, language, hashtags, media type, or verified users for search runs.
5. Set maxItems and limit to control output size. The Actor automatically increases the effective page count when maxItems needs more pages than maxPages.
6. Run the Actor and use the dataset from Apify exports, API, integrations, or scheduled tasks.

No scraping infrastructure setup is required.

Need a custom plan, custom limits, or a tailored data workflow? Contact contact@simoit.tech.

Input

• inputTargetType (string, optional, default: search): search for keyword/query collection or tweet_replies for replies to specific tweets.
• searchTerms (string, optional): Main search phrase (or multiple comma/newline terms). Use this or rawQuery; avoid duplicating the same query in both.
• rawQuery (string, optional): Full X/Twitter advanced search string used as-is. Can be used on its own.
• conversationIds (string, optional): Advanced search compatibility field. Internally converted to conversation_id:<id> search queries. For real tweet replies, use tweetIds with inputTargetType: "tweet_replies".
• tweetIds (string, optional): Tweet IDs or tweet URLs (comma/newline). Used with inputTargetType: "tweet_replies" to call the tweet replies endpoint.
• tweetUrls (string, optional): X/Twitter status URLs (comma/newline). Used with inputTargetType: "tweet_replies".
• startUrls (string, optional): X/Twitter search URLs (x.com / twitter.com), comma-separated or new lines.
• sort (string, optional, default: latest): latest or top.
• fromUsers (string, optional): Comma-separated usernames for from: filter.
• toUsers (string, optional): Comma-separated usernames for to: filter.
• mentioningUsers (string, optional): Comma-separated usernames to be mentioned.
• startDate (string, optional): Start date. Accepts YYYY-MM-DD, D/M/YYYY, or M/D/YYYY.
• endDate (string, optional): End date. Accepts YYYY-MM-DD, D/M/YYYY, or M/D/YYYY.
• minimumLikes (integer, optional): Minimum likes threshold.
• minimumRetweets (integer, optional): Minimum retweets threshold.
• minimumReplies (integer, optional): Minimum replies threshold.
• onlyImage (boolean, optional, default: false): Return only image tweets.
• onlyVideo (boolean, optional, default: false): Return only video tweets.
• onlyVerifiedUsers (boolean, optional, default: false): Return only verified-account tweets.
• includeReplies (boolean, optional, default: true): Include replies.
• includeRetweets (boolean, optional, default: true): Include retweets.
• withinRadius (string, optional): Geo filter, format: lat,lon,radius (for example 52.23,21.01,10km).
• page (integer, optional, default: 1): Starting page number.
• limit (integer, optional, default: 20, max: 100): Records per page.
• maxPages (integer, optional, default: 1): Minimum number of pages to fetch. If maxItems requires more pages, the Actor automatically increases the effective page count.
• maxItems (integer, optional): Hard cap for total output records.

Legacy compatibility:

• The Actor still accepts aliases such as author, inReplyTo, mentioning, start, end, since, until, and minimumFavorites.
• Those aliases are supported for backward compatibility, but they are intentionally not exposed in the public input UI.

Filters and pagination

• search target: rawQuery, searchTerms, conversationIds, startUrls
• tweet replies target: inputTargetType: "tweet_replies" with tweetIds or tweetUrls
• advanced query helpers: rawQuery, exactPhrase, excludeTerms, hashtags, language
• author/mention filters: fromUsers/author, toUsers/inReplyTo, mentioningUsers/mentioning
• date filters: startDate/start/since, endDate/end/until accepted formats: YYYY-MM-DD, D/M/YYYY, and M/D/YYYY
• quality filters: minimumLikes/minimumFavorites, minimumRetweets, minimumReplies
• media/account filters: onlyImage, onlyVideo, onlyVerifiedUsers
• inclusion switches: includeReplies, includeRetweets
• geo filter: withinRadius
• page controls: page, limit, maxPages, maxItems

Example input

{
  "searchTerms": "open source ai agents",
  "exactPhrase": "agent memory",
  "excludeTerms": "spam,fake",
  "hashtags": "ai,agents",
  "language": "en",
  "sort": "latest",
  "fromUsers": "openai,apify",
  "startDate": "2026-02-01",
  "endDate": "2026-02-20",
  "minimumLikes": 10,
  "includeReplies": true,
  "onlyVideo": false,
  "maxItems": 50
}

Collect replies for one post:

{
  "inputTargetType": "tweet_replies",
  "tweetIds": "2070555273467687257",
  "page": 1,
  "limit": 100,
  "maxItems": 300
}

Suggested Apify task presets

These are reusable task ideas you can create from this Actor. They are suggested presets, not separate Actors.

Task	Input preset	Expected output
Brand monitoring by keyword	searchTerms, language, maxItems, optional minimumLikes	Recent tweets mentioning a brand, product, or executive
Campaign hashtag analysis	hashtags, startDate, endDate, sort: latest	Tweets from a campaign window with engagement counters
Competitor mention tracking	searchTerms, fromUsers or mentioningUsers, maxItems	Mentions and conversations around competitor accounts
Tweet replies monitoring	inputTargetType: tweet_replies, tweetIds, maxItems	Replies for one or more specific posts
High-engagement tweet discovery	searchTerms, sort: top, minimumLikes, minimumRetweets	Strong-performing tweets for a topic or market
Video tweet collection	searchTerms, onlyVideo: true, maxItems	Video posts matching a query

Related Actors

• Need tweets from one specific profile instead of broad search results? Use Profile Scraper.
• Need account metadata, followers, or following instead of tweets? Use User Scraper.
• Need posts from a curated X list? Use List Scraper.
• Need preset or country-level trend feeds before drilling into tweets? Use Trends Scraper or Global Trending Scraper.

About SIMO IT

SIMO IT delivers practical scraping and automation tools that help teams extract value from social platforms faster.

FAQ

Is this an official X/Twitter API?
No. This is an Apify Actor for collecting X/Twitter data. It is not an official X/Twitter API, and you are responsible for using the data in a compliant way.

Can I export tweets as JSON or CSV?
Yes. Results are stored in the Apify dataset, so you can use Apify exports such as JSON, CSV, Excel, XML, RSS, or HTML table where supported by your Apify workflow.

Can I run this Actor by API, schedule it, or integrate it with other tools?
Yes. You can run it manually, call it through the Apify API, create reusable Apify tasks, schedule recurring runs, and connect dataset output to Apify integrations or your own workflows.

Which input should I use first?
Use searchTerms for simple keyword searches, rawQuery for advanced X/Twitter search syntax, and startUrls when you already have search URLs. Use inputTargetType: "tweet_replies" with tweetIds or tweetUrls when you want replies for a specific post.

Can I collect more than one page of results?
Yes. Use page, limit, and maxPages for pagination. Use maxItems as the simplest hard cap for total dataset records. If maxItems needs more pages than maxPages, the Actor automatically increases the effective page count.

How do I control output size and cost?
Use narrower queries, date ranges, author filters, engagement filters, limit, maxPages, and maxItems. For most runs, start with maxItems and increase it only when the output quality is confirmed.

Can I narrow results to high-quality tweets only?
Yes. Use engagement filters like minimumLikes, minimumRetweets, and minimumReplies, or use sort: top.

Can I include or exclude replies and retweets?
Yes. Use includeReplies and includeRetweets.

What are the practical limitations?
Results depend on X/Twitter availability, the query, selected filters, date range, and pagination settings. Very broad or very old searches can return fewer useful records than focused queries.

Does this Actor support legacy alias fields?
Yes. It supports aliases like author, inReplyTo, mentioning, start/end, since/until, and minimumFavorites.