Twitter/X Profile Scraper

Thirdwatch portfolio: 5K users across 88 public Actors, 2M+ records delivered, and >99% run success. Explore all Thirdwatch Actors.

Scrape public posts from any Twitter/X profile — text, likes, retweets, replies, views, bookmarks, posted dates, and media URLs. No login or API key.

What you get

Structured post data from any public Twitter/X profile. Pass a list of handles and get back every post's text, engagement metrics, posting date, media URLs, and author info. Useful for monitoring, research, and content analysis without depending on the paid X API.

Two modes:

• posts (default) — one row per post from each handle's timeline, paginated. Set maxTweetsPerUser above 100 to walk months back through a timeline.
• profiles — one row per handle with the account's public profile: follower and following counts, post count, bio, location, website, verification and account age. No timelines are read, so it is one request per handle.

Output fields

Field	Description
text	Tweet text
likes	Number of likes
retweets	Number of retweets
replies	Number of replies
posted_date	ISO 8601 tweet timestamp
media_urls	Attached media URLs
author	Author handle
url	Tweet URL
author_name	Display name from the public tweet payload
author_verified	Public verified flag when available
views	View count, from X's own counter
bookmarks	Bookmark count
quotes	Quote-post count
is_reply / is_retweet / is_quote	Post type flags
quote_tweet_url	The post this one quotes
hashtags / mentions / external_urls	Parsed entities
video_url	Highest-bitrate MP4 when the post carries video
author_followers	Author's follower count
author_bio, author_location, author_website	Author profile fields
dataSource	graphql_user_tweets, graphql_tweet, or the syndication fallback

profiles mode fields

Field	Description
username, user_id, name	Account identity
followers, following	Audience counts
tweet_count, media_count, likes_count	Activity counts
bio, location, website	Profile text
verified, verified_type, is_blue_verified, protected	Account flags
profile_image, banner_image, created_at, profile_url	Assets and metadata

Example output

{
    "text": "Excited to announce our latest product launch...",
    "likes": 15000,
    "retweets": 3200,
    "replies": 800,
    "posted_date": "2026-04-08T14:30:00Z",
    "media_urls": ["https://pbs.twimg.com/media/..."],
    "author": "elonmusk",
    "url": "https://twitter.com/elonmusk/status/..."
}

Input parameters

Parameter	Required	Description
usernames	Yes	List of Twitter/X handles to scrape (without the @ symbol). Example: ["elonmusk", "sundarpichai"].
mode	No	posts (default) for timelines, profiles for account details only.
maxTweetsPerUser	No	Maximum posts to extract per profile. Default 15, max 3000.
tweetUrls	No	Individual post URLs or IDs to fetch. Can be combined with usernames.
sinceDate	No	Drop posts older than YYYY-MM-DD. Pagination stops at this boundary, so it makes deep runs cheaper.
includeReplies, includeRetweets, onlyReplies, onlyWithMedia, minLikes	No	Post filters.
proxyConfiguration	No	Defaults to the standard Apify Proxy. The endpoint this Actor uses is not IP-gated, so the expensive residential group is not needed.

Use cases

• Social media analysts: Track engagement metrics and posting patterns per account.
• Brand monitoring: Watch official brand accounts and executive handles for announcements.
• Content researchers: Collect tweet corpora for sentiment and topic analysis.
• Journalists: Pull public timelines for background and quote verification.
• Investor research: Monitor founder and exec accounts for product and company signals.

Use cases & recipes

Step-by-step guides on thirdwatch.dev/blog:

• Build a Twitter Data Pipeline for Research (2026 Guide)
• Monitor Influencer Tweets at Scale (2026 Guide)
• Scrape Twitter/X Profiles Without API at Scale (2026)
• Track Brand Mentions on Twitter/X at Scale (2026)

-end

Pricing

Pay-per-result pricing. Tiered discounts apply automatically based on usage volume.

Tier	Price per result
FREE	$0.003
BRONZE	$0.0025
SILVER	$0.002
GOLD	$0.0016

Limitations

• Only public accounts — protected accounts cannot be scraped, and are reported as such rather than returned empty.
• No keyword search. X gated every unauthenticated search surface: its SearchTimeline GraphQL operation, and every legacy REST and syndication search path, refuse a guest session. This Actor is profile-first by necessity, not by preference. Anything advertising logged-out X keyword search is either using an account pool or a third-party mirror.
• No replies to someone else's post. TweetDetail is gated the same way. Replies written by a scraped handle do appear in its timeline.
• No follower or following lists — also gated.
• A handful of very large accounts are served from an X edge cache that returns roughly 100 posts and no pagination cursor. For those, ~100 posts is the ceiling regardless of maxTweetsPerUser.
• When the guest timeline returns nothing, the Actor falls back to X's syndication embed. That path is heavily rate-limited, so it is a backstop rather than the main route.

Compared to alternatives

• vs. apidojo/tweet-scraper ($0.0004/result BRONZE, 48K users): That actor is cheaper per tweet with a broader crawl model (search, lists, conversations). This actor is profile-first: give it a list of handles and get back one clean row per tweet, which is the simpler shape for most monitoring and analytics pipelines.

Pairs well with Google News Scraper and Reddit Scraper for broad social listening.

FAQ

Do I need X API credentials? No. The actor works without login or API keys.

Does it include replies and retweets? Replies from the handle are included when publicly visible. Retweets appear as separate rows with the original author attributed in text/url.

How many posts can I pull per profile? The timeline is paginated, so maxTweetsPerUser can go well past 100 — hundreds of posts, months back. A few very large accounts are edge-cached by X at ~100 posts with no cursor.

Can I search by keyword instead of handle? No. X does not serve keyword search to logged-out clients on any endpoint, so this Actor does not pretend to. It is profile-first. For keyword discovery use a news or search scraper.

Do I need residential proxies? No. The public endpoint this Actor uses answered 10/10 requests through ordinary Apify datacenter IPs in testing.

Last verified: 2026-09

More scrapers at thirdwatch.dev.