Tweet Scraper

Collect tweets for any topic and narrow the results with query, author, date, engagement, and media filters to keep the output analysis-ready.

About SIMO IT

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

Features

• find tweets by keyword or query phrase
• collect by conversation IDs (conversation_id:<id>)
• collect tweets directly from selected handles
• narrow results to specific authors, recipients, or mentions
• limit data to a selected date range
• filter for stronger engagement signals
• focus on media type (image/video)
• paginate through larger result sets for deeper analysis

Use cases

• brand and campaign monitoring
• sentiment and reaction analysis
• market research for content and sales teams
• building datasets for AI and classification pipelines

Output

A clean list of matching tweets, ready for reporting, analytics, and downstream automation.

How to use

1. Open the Actor on Apify.
2. Provide searchTerms, conversationIds, or startUrls.
3. Add optional filters and pagination based on your use case.
4. Run the Actor and use the dataset output in Apify.

No technical setup is required from your side. Backend infrastructure is managed by SIMO IT.

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

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.

Input

• searchTerms (string, optional): Main search phrase (or multiple comma/newline terms).
• conversationIds (string, optional): Conversation IDs (comma/newline), internally converted to conversation_id:<id>.
• 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 in YYYY-MM-DD.
• endDate (string, optional): End date in YYYY-MM-DD.
• 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): Maximum number of pages to fetch.
• 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: searchTerms, conversationIds, startUrls
• author/mention filters: fromUsers/author, toUsers/inReplyTo, mentioningUsers/mentioning
• date filters: startDate/start/since, endDate/end/until
• 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",
  "conversationIds": "1891042203344556600",
  "sort": "latest",
  "fromUsers": "openai,apify",
  "startDate": "2026-02-01",
  "endDate": "2026-02-20",
  "minimumLikes": 10,
  "includeReplies": true,
  "onlyVideo": false,
  "maxItems": 50
}

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"
}

FAQ

Do I need my own backend or API setup?
No. This Actor is ready to run on Apify, and backend infrastructure is managed by SIMO IT.

Can I collect more than one page of results?
Yes. Use page, limit, and maxPages to control pagination.

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

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