Twitter Profile Scraper - Tweets, Metrics & Analysis, No Login
Pricing
from $0.40 / 1,000 tweet, reply or quote rows
Twitter Profile Scraper - Tweets, Metrics & Analysis, No Login
Twitter (X) profile scraper that needs no login: a profile's recent tweets with likes, retweets, views and dates, the profile row, topic, sentiment and bot-signal rows. Add your own X session cookies for search, replies, quotes, followers and exact date windows. JSON, CSV, Excel.
Pricing
from $0.40 / 1,000 tweet, reply or quote rows
Rating
0.0
(0)
Developer
Daniel Carter
Maintained by CommunityActor stats
0
Bookmarked
5
Total users
2
Monthly active users
15 days ago
Last modified
Categories
Features
Share
Twitter profile scraper without login: put in handles and get each profile row and its recent tweets with likes, retweets, replies, views and dates (measured 2026-11-05: NASA returned 149 rows in one run, no cookies). Search, reply threads, quotes, followers and exact date windows need your own X session cookies in cookies.
Run price = $0.005 setup + $0.01 per completed lookup + fees for delivered rows.
Search and profile timeline tweets are checked against the date window before delivery. Those outside it are dropped and incur no tweet-row charge. Reply and quote rows can fall outside that window and are billed when delivered. Direct tweet URLs currently return the requested tweet without applying the date filter.
A lookup with no delivered tweets still has a $0.01 query-completed fee when its query-summary is delivered. This is not the total run price: a separate $0.005 run-started fee applies after the X web client is ready, and any delivered profile, follower or paid analysis rows add their listed fees. A run with one completed empty lookup and no other billable rows costs $0.015. One returned profile with no tweets and no followers costs $0.017. Notice rows and free-plan analysis previews are not billed.
This Actor is not affiliated with, endorsed by, or sponsored by X Corp. "X" and "Twitter" only describe what it works with.
Free plan vs paid plans
| Free Apify plan (a preview) | Any paid Apify plan | |
|---|---|---|
| Tweets per run | Up to 25 | Up to your maximums (20,000 per search term, 3,200 per profile) |
| Search (needs your own X cookies) | Locked: search with your own X session is a paid feature. Pasted cookies are ignored, so your X account is never used | Every page of every search term, exact date window, Latest or Top |
| Profiles and tweet URLs | Up to 5 in total, within the 25 tweets | Up to 200 each, full timelines |
| Reply threads, quote tweets, followers | Locked | Yes, one row each |
| Analysis rows | One preview row per type (5 types) for the whole run, marked preview: true with total | Every row of every type |
| Author profile rows | Up to 5 | One per unique author |
Every free run ends as SUCCEEDED with a free-plan-preview notice row and status message that count what a paid run would have added for the same input, for example: "Free preview: 25 tweets and 5 analysis rows (5 of 62). Paid plans get ~2,400 more tweets, 316 replies, 74 quotes and 57 more analysis rows for this input." The tweet estimate comes from X's own numbers: the profile's tweet count, or whether the timeline offered another page. If you entered more than 5 profiles and tweet URLs, the notice counts how many more a paid run would have looked up. If you entered search terms, the notice also says "Search with your own X session is a paid feature" and how many terms were locked. A free run with only search terms ends right away with that notice and pays only the $0.005 run-started fee. Preview analysis rows and notice rows are never charged.
What you get
| Input | Without login | With your own X session cookies |
|---|---|---|
Profiles (NASA, @NASA, profile URL) | Profile row + timeline tweets | + reply threads, quote tweets, followers |
| Tweet URLs | The tweet | + its reply thread and quote tweets |
| Search terms (any X search syntax) | Not available: X only answers search to signed-in sessions | Search with an exact date window, Latest or Top (paid plans) |
Every run also adds one profile row per unique author (followers, following, account age, verification, bio) taken from tweets already fetched, so no extra requests. Each query also gets analysis rows (free plan: one preview row per type):
- Topic clusters: the hashtags, words and link domains that group the conversation, with size, engagement and top tweet.
- Influencer ranking: authors ranked by engagement in your sample, with engagement per follower.
- Complaint and sentiment themes: refunds, bugs, outages, support, price, cancellations, scams and praise, each with sample tweets (English word lists).
- Time trend: hourly or daily buckets with engagement and spike flags.
- Bot-suspicion signals: new accounts, extreme posting rates, default avatars, copy-paste text. A signal, not a verdict.
How the date window works
since(inclusive) anduntil(exclusive) are turned into exact UTC timestamps and sent to X assince_time:/until_time:. X's plainsince:/until:date operators are read in a time zone you do not control; in our test only 4.3% of the results they returned fell inside the UTC window.- Each search or profile timeline tweet is checked again against its applicable window using createdAt. Out-of-window tweets from these paths are dropped before delivery. Direct tweet URL lookups currently do not apply this filter. Reply and quote rows are not excluded by their dates and incur the normal row fee when delivered. When since or until is supplied as an input field, insideWindow reports the row's position relative to that window; otherwise it can be null.
- The query-summary row says what happened: window,
receivedFromX,droppedOutsideWindow,droppedByFilters,duplicatesSkipped, delivered counts, andstoppedBy.
The engagement filters minLikes, minRetweets and minReplies judge a retweet by the counters of the original tweet it repeats, not by the retweet's own counters (X leaves those near zero).
Quoted or retweeted originals inside a tweet are kept as fields (quotedTweet, retweetedTweet) and never used for the window check. Reply and quote rows are billed at the same $0.0004 row rate even when their dates fall outside the window. Direct tweet URLs also bypass the date filter.
Common complaints about tweet scrapers, and what this Actor does
| Complaint pattern in public reviews (paraphrased) | Here |
|---|---|
| Date filter ignored, results outside the requested range | Exact epoch window + a second check for search and profile timeline tweets; drops are published on the summary row. Delivered replies, quotes and direct URL tweets are billed even outside the window |
| Charged for "noResults" or demo rows | Completed empty lookups incur the $0.01 query fee. The $0.005 setup fee and any other delivered-row fees are separate. Notice rows are never billed. |
| The free-plan price is about 100 times the listed price | One price on every plan. The free plan is a capped taste: same price, fewer rows |
| Asked for 1,000 results, got 100 | Pages are walked until your maximum, the end of results, or X's limit; stoppedBy tells you which |
Pricing (pay per event, same price on every plan)
| Event | Price | When |
|---|---|---|
run-started | $0.005 | Once after X web client setup succeeds, including guest setup when a paid run has profiles or tweet URLs plus search terms but lacks the required session cookies. No fee if setup fails on our side. A run refused for its input pays it once too: nothing to collect, an invalid date window, a paid run with only search terms and no usable session cookies, or a free-plan run with only search terms (it ends SUCCEEDED with a notice saying the start fee was charged). |
query-completed | $0.01 | Per search term, input profile or tweet URL for which lookup work produces a query-summary, including no-match results and partial results reported in that summary. Skipped searches do not incur this fee. Separate setup and delivered-row fees still apply. |
tweet-row | $0.0004 | Per unique delivered tweet, reply or quote row. Search and profile timeline tweets outside the date window are dropped. Replies and quotes may be outside the window and are still billed. Direct tweet URLs currently bypass the date filter. |
profile-row | $0.002 | Per profile or follower row delivered |
analysis-row | $0.02 | Per analysis row delivered on paid plans. Free-plan preview rows are not charged |
access-response | $0.01 | Per input profile, tweet URL or search term whose very first X request was refused (X rate limit, or X rejected your session cookies), so the lookup could not start. Comes with an access-response row naming the refusal. Never together with query-completed for the same input; network errors and our own failures are not charged |
On a paid plan, a run containing profiles or tweet URLs plus search terms without both required cookies (auth_token and ct0) skips those searches. If guest client setup succeeds, it still incurs the $0.005 setup fee, but no query-completed fee for the skipped searches. Runs rejected before setup for missing valid targets, an invalid date window, only search terms without usable session cookies, or only search terms on the free plan pay the $0.005 run-started fee once and nothing else.
If the platform restarts a run (for example a server migration), the run goes on from its own dataset: an input that already has its query-summary or access-response row is not looked up again, rows already delivered are not delivered or charged again, and the setup fee is charged once.
Example: one search term, 500 tweets, 10 threads with 400 replies and quotes, 150 author profiles, 20 analysis rows costs about $0.005 + $0.01 + 900 × $0.0004 + 150 × $0.002 + 20 × $0.02 = $1.08. Set "Maximum cost per run" in Apify to cap any run; the Actor stops cleanly at that cap.
Free plan
Up to 25 tweet rows and 5 profile rows per run from at most 5 profiles and tweet URLs, which work without login. Search, reply threads, quote tweets and followers are locked, and pasted cookies are ignored, so a free run never acts as your X account. Each analysis type shows its first row once per run as a preview (preview: true, shown: 1, total: rows a paid run gets for that query), not charged; further queries count their analysis rows as locked. The run ends as SUCCEEDED with a free-plan-preview notice row and status message listing what a paid run would have added: estimated more tweets, the reply and quote counts on the tweets you got, locked analysis rows and, with "Search with your own X session is a paid feature", the number of locked search terms.
Your X session cookies
X answers search, reply threads, quotes and followers only to signed-in sessions. On a paid plan, paste your own x.com cookies into cookies: a cookie-editor JSON export, or a header like auth_token=…; ct0=… (both are required). The free plan ignores cookies.
- The run acts as your X account. You accept the risk of X limiting or locking that account, and you are responsible for complying with X's terms.
- Requests follow X's own per-account limits (search: 50 requests per 15 minutes). When a limit is reached the run waits for the reset (up to
maxRateLimitWaitSeconds) or skips that step with a notice row. - A query that hits the search limit keeps its partial results and a reason row (
stoppedBy: "rate-limit"on its query-summary row), and the run still ends as SUCCEEDED. - The value is stored encrypted by Apify (secret input) and is never written to the log, the dataset or the key-value store.
Input example
{"searchTerms": ["\"customer support\" (acme OR acmeapp) -filter:retweets"],"since": "2026-09-01","until": "2026-09-08","searchMode": "Latest","maxTweetsPerQuery": 500,"threadsPerQuery": 10,"maxRepliesPerTweet": 100,"minLikes": 2,"cookies": "auth_token=…; ct0=…"}
Output example (tweet row)
{"rowType": "tweet","id": "2102882545427714266","url": "https://x.com/NASA/status/2102882545427714266","text": "Welcome to the Artemis Accords, Croatia 🇭🇷 …","createdAt": "2026-09-23T22:07:23.000Z","lang": "en","conversationId": "2102882545427714266","isReply": false,"isQuote": false,"isRetweet": false,"likeCount": 2219,"replyCount": 57,"retweetCount": 227,"quoteCount": 29,"bookmarkCount": 167,"viewCount": 291797,"totalEngagement": 2699,"urls": ["https://go.nasa.gov/3VcvAQn"],"media": [{ "type": "photo", "url": "https://pbs.twimg.com/media/HS7wh0rXMAA61bq.jpg", "width": 2000, "height": 1125 }],"author": { "userName": "NASA", "followers": 92373166, "isBlueVerified": true, "verifiedType": "Government" },"matchedQuery": "@NASA","insideWindow": null,"collectedAt": "2026-09-24T01:20:00.000Z"}
Reply rows add parentTweetId, threadRootId and isDirectReply; quote rows add parentTweetId. Row types: tweet, reply, quote, profile, follower, topic-cluster, influencer-rank, sentiment-theme, time-trend, bot-signal, query-summary, notice. The dataset has table views for tweets, profiles, summaries and analysis. Export as JSON, CSV or Excel.
Responsible use
The data is public X content collected at your request. You are responsible for lawful use of it (GDPR, CCPA and other law), for the terms of the sites involved, and for any use of your own X session. Do not use it for harassment, stalking or spam.
Leave a review
If this Actor saved you time, a short review on its Apify Store page helps other people find it. If something breaks, open an issue on the Actor's Issues tab and include the run ID; we fix scrapers quickly when X changes.