Twitter replies scraper for X replies, comments & whole conversations from $0.00015 per delivered reply. Read Twitter replies without an account. Paste post URLs in bulk, use 25+ filters & export flat rows. World's fastest & cheapest X (Twitter) scraper service. Not affiliated with X Corp.
2026-11-13. A run with a filter such as sinceTime or minLikes now saves
its first replies before it has read the whole thread. Before, it saved none
until it had read every reply, which took longest on posts with many replies.
2026-11-11. An edited post's likeCount, replyCount, retweetCount,
quoteCount & bookmarkCount now match x.com. Each adds the counts of the
earlier versions, which previousCounts still lists. Before, each held only
the newest version's count.
2026-11-11. A reply read now returns a slow first page sooner. The next page
carries on from where that page stopped.
2026-11-11. Reply reads with a date range now get replies X lists by ID.
Before, they could miss 1 & still say they read every reply.
2026-11-11. A reply read now returns a live reply it could miss before.
Before, it could be missing from 1 read & back in the next.
2026-11-10. The page's search title & summary now name X (Twitter) & the
searched phrase.
2026-11-10. A thread run now continues with auto when X's thread view ends
before maxItems. Before, it stopped there & said it collected every
available result. A large post gave 400 of 6,000 replies.
2026-11-09. A reply read now follows a thread past 1,000 pages until it reads
the last reply, your maxItems or your run's time limit. Before, a target
stopped at 1,000 pages with page_limit and left the later replies unread.
2026-11-08. The Actor page now says you need no X account.
2026-11-08. Run logs now hide more kinds of sensitive text in more input
formats.
2026-11-08. A run stopped by your maximum cost per run now says so. Before, it
could say a target reached the page limit.
2026-11-08. A read of many posts that saves more than 16,384 replies now stays
within its 256 MB of memory. Before, such a read could end with exit code 137
and keep only the replies it had saved by then.
2026-11-08. A reply read now leaves out a reply its author hid after an
earlier read saw it. Before, such a reply could come back with no sign that it
was hidden.
2026-11-07. A reply read now returns replies X stopped listing once Xquik has
seen them in an earlier read. It returns each only after X confirms the reply
is live and still answers the post. Before, such replies could be missing from
a whole read.
2026-11-07. A run that Apify restarts now charges each result once. Before,
rows saved just before the restart could be charged a second time.
2026-11-06. A likes run now reads on past a page whose new replies only tie
the lowest row it keeps. Before, it could stop there and miss a more liked
reply on a later page.
2026-11-06. A run sorted oldest first now shows how many replies it has read
while it holds them. It also says why it saves them only once the read ends.
Before, its status said 0 replies so far for the whole read.
2026-11-06. Apify now refuses a maximum cost per run that can't pay for 1
result and the platform usage before it. Its error names the least limit that
can. Before, such a run started and returned nothing.
2026-11-06. A run no longer writes an error to its log when a progress report
to Xquik fails to send. Results were never affected.
2026-11-03. A profile link in usernames, like x.com/nasa, now reads that
account. Before, the run skipped it.
2026-11-03. A skipped input now says what was wrong, like a link to another
site or to a post.
2026-11-02. Posts with no replies finish in about half the time.
2026-11-02. Runs over many posts finish faster.
2026-11-01. Runs that sort direct replies by likes return their most liked
replies faster and miss fewer of them.
2026-11-01. The "Why use" section adds the run cost estimate, multi-target
runs & field descriptions. It also says runs count the replies they didn't
reach.
2026-11-01. Runs no longer wait out their time limit when hidden replies stop
loading.
2026-10-31. If a run stops early, its status now counts the replies it didn't
reach. X's reply count sets the total. When a date sort may skip replies
between rows, the status says so.
2026-10-30. The Store description now starts with "Twitter replies scraper".
Runs, inputs & prices stay the same.
2026-10-28. A thread whose read of nested replies stopped early stays partial,
even once its direct replies are read to the end.
2026-10-28. A thread whose first read stopped early now ends as finished once
the last read reaches the thread's end. Its status now says how many replies X
hides. Before, it said X served only part of the thread.
2026-10-28. Posts that belong to a live event, such as an election, carry
liveEventContext. It has the event's title, url & imageUrl.
2026-10-28. Runs without a time limit no longer fail targets as busy while
their other targets still get results.
2026-10-28. The run status now says replies to posts older than 7 days can be
incomplete.
2026-10-28. The dataset schema now describes the start & end offsets of each
text highlight.
2026-10-27. The README adds a "Why use" section of highlights & features above
its data.
2026-10-27. Runs with a time limit no longer fail targets as busy.
2026-10-27. A reply author's affiliate label now lists the other labels X
shows beside it, each with its text, badge, link & label type.
2026-10-26. The README now lists what you get from each run. Input & output
field descriptions now say what you get.
2026-10-24. Each photo in media carries editedWithNativeEditor: true when
its author edited it in X's own editor.
2026-10-21. Large runs & runs with a problem save run-report again. It
counts failed targets by cause in targetFailureKinds.
2026-10-21. softIntervention holds the label X shows on a tweet it limits.
2026-10-18. A run for all replies of a large post now saves every nested reply
too, up to maxItems. Before, it could miss nested replies.
2026-10-18. A run now says X was unavailable when X's outage stops a target.
2026-10-17. A run now ends as soon as its work is done, even while Xquik is
down.
2026-10-17. Each post lists the counts X did not send in unknownCounts.
Those counts read 0, so treat them as unknown. Rows in snake_case name them
like their fields, such as bookmark_count.
2026-10-14. A profile link by user ID, like x.com/i/user/11348282, now reads
that account.
2026-10-14. A slow X answer no longer holds up a run's replies.
2026-10-14. A run with missing replies now gives the right reason, & no longer
says that X hides them.
2026-10-14. The README says the prefilled form holds a conversation we tested.
2026-10-14. The Store text & the top of the README use plainer sentences.
2026-10-13. Each post's author now holds profilePictureOriginal, the profile
picture at full size, to download. profilePicture stays the 48 px image.
2026-10-13. An account can be named by its user ID of 16 to 19 digits, like a
handle. This works in usernames & profile links.
2026-10-13. A run with scopedirect or collectionStrategyreplies says
how many replies X hides. Before, an empty one said no replies matched.
2026-10-13. New example tasks collect giveaway replies & read Twitter comments
without an account.
2026-10-13. The Store title reads X (Twitter) Replies Scraper, & the README
opens with Twitter replies & comments.
2026-10-13. Field help & the README drop colons & semicolons.
2026-10-13. The run status drops its colons. An aborted run starts Aborted.,
& the batching tip has no label.
2026-10-13. An empty run of a post whose replies X hides now says so in its
status. Before, it said no replies matched.
2026-10-12. Paging can no longer loop until the run's time runs out. The run
never charges a row twice.
2026-10-12. sortBy, queryType, includeNestedReplies,
includeRepliesOfReplies & outputVariant take effect when sort, scope &
outputMode stay at their defaults. Before, the default won.
2026-10-12. The Actor reads more input names of other reply Actors. They are
resultsPerCategory, includeSourceTweet, excludeOpSelfReplies, depth,
onlyDirectReplies & twitterUrl. It also reads the sort words top,
newest & mostLiked. A category that is another Actor's job stops the run
before any read or charge.
2026-10-12. Shape your rows with fields, omitFields, renameFields,
flatten, joinFields & constantFields. Name totalEngagement,
engagementRate or engagementPerView in fields to add it.
2026-10-12. Authors carry email & contactInfo, the emails, phones & links
their profile publishes, when X sends the bio.
2026-10-12. subscriberBadge names the creator whose Subscriber badge a reply
shows.
2026-10-11. Limited likes runs of direct replies no longer miss top replies
on large threads.
2026-10-11. The schema says X sends source, the posting app, for some posts
only.
2026-10-11. A run whose posts all ended no longer writes an empty
next-cursors, so runs cost less.
2026-10-10. Replies carry cashtagAttachments, the price charts their authors
attached to cashtags. Tags in entities, hashtags included, add their
SmartTag id & active when X sends them.
2026-10-09. Each Grok image in media carries grokImageAnnotation, the
prompt it came from, when X sends one.
2026-10-09. Runs of all or nested replies by relevance or latest also save
each page as it arrives, with each reply's depth.
2026-10-09. Runs of direct replies by relevance or latest save each page as it
arrives. A stopped run keeps what it read.
2026-10-09. Unfiltered runs of direct replies sorted by likes finish sooner
with a limit.
2026-10-09. Filtered runs of direct replies finish sooner.
2026-10-09. A filtered run's status counts the replies it read, not only the
ones that matched your filters.
2026-10-09. Set mediaType to none to keep only text replies, without media
or links.
2026-10-09. Successful runs with rows end their status with a short review
request.
2026-10-09. The default auto strategy adds the replies the post's author
hid, as hiddenReply rows. Set includeHiddenReplies: false to skip them.
2026-10-08. Long threads return more replies.
2026-10-08. The Actor skips post IDs X cannot have, such as 20-digit ones, &
names them.
2026-10-08. Replies sorted by likes or oldest first now finish faster on long
threads. You get the same replies in the same order.
2026-10-07. Stalled reads now recover on their own, so runs lose less time.
2026-10-07. Community tweets can carry communityName beside communityId
when X sends the community's name.
2026-10-07. A run that reads every target & finds no reply writes no
diagnostics record. Its status says why, & the run costs less.
2026-10-05. Runs with many targets save progress less often, finish sooner &
cost less.
2026-10-05. Large runs upload their rows faster.
2026-10-05. Runs sorted by most liked now find more liked replies.
2026-10-05. Runs of under 5 IDs or handles end with a tip to batch them.
2026-10-04. A run on a renamed handle now saves the replies X shows for it.
2026-10-04. A run whose posts all ended writes next-cursors only when it
keeps its report, so small runs cost less.
2026-10-04. The Actor version in diagnostics & run reports is now the Apify
build number.
2026-10-04. A run no longer stops early when an upload's answer is lost. Its
rows are charged once.
1.2.125, 2026-10-04
collectionStrategy: "hiddenReplies" returns the replies a post's author hid.
Each one is a hiddenReply row at the usual row price.
1.2.124, 2026-10-04
Every run uses 256 MB again, which is faster & more reliable for small runs.
1.2.123, 2026-10-01
When Xquik stays busy, each retry waits longer than the last.
If Xquik stays busy too long, that target fails & the run says why.
Busy answers are never charged.
1.2.122, 2026-09-30
A run with rich output keeps its run-report.
1.2.121, 2026-09-30
A run near its time limit stops before a read it can't finish.
1.2.120, 2026-09-29
A run that started late says how long it waited, out of its time limit.
1.2.119, 2026-09-29
Requests to Xquik never follow a redirect, so the key stays with Xquik.
1.2.118, 2026-09-29
A run waits out a brief Xquik outage instead of failing.
Rows saved before an outage stay saved & are charged once.
1.2.117, 2026-09-29
Runs sorted by likes or oldest, or with nested scope, keep 256 MB.
Runs with more than 5 targets keep 256 MB, whatever field names them.
1.2.116, 2026-09-29
Runs up to maxItems 50 with up to 5 targets use 128 MB & cost less.
1.2.115, 2026-09-29
New outputMode: "rich" keeps every full column & adds hasCommunityNotes,
quotedTweetPermalink, unavailableAuthorId & media sourceUser.
Full, the default, & every other output keep their rows unchanged.
1.2.114, 2026-09-29
The README names the Actor as Xquik's X Reply Scraper & adds a how-to & FAQ.
The README says the prefilled form returns up to 1,000 rows, as the form sets.
1.2.113, 2026-09-29
Runs sorted by most liked stop once X's most liked replies fill the limit.
Runs with a reply author finish sooner.
1.2.112, 2026-09-28
A run that finds nothing skips run-report, so it costs less in Apify usage.
1.2.111, 2026-09-28
Runs under 34 results cost less in Apify usage, with no progress saves.
1.2.110, 2026-09-28
An aborted run's status counts its saved results, even during a slow upload.
1.2.109, 2026-09-28
A missing post or account no longer counts as a failure. The status names it &
says to check the handle, ID or URL.
1.2.108, 2026-09-28
Replies now come back for more posts, from a URL or an ID.
1.2.107, 2026-09-27
During a run, the status shows how many results it has collected so far.
The status says when the run waits to retry.
1.2.106, 2026-09-27
The new alwaysSaveRunRecords input keeps run-report on every run.
1.2.103, 2026-09-27
URLs without https://, such as x.com/nasa, now work.
Post URLs in capitals & Article URLs now read that post's replies.
A post URL with a broken ID no longer reads its author's replies.
Profile URLs whose handle is all digits, such as x.com/1234567, now work.
The run lists each input it cannot read & says how to fix it.
With nothing to read, the run writes a free diagnostic with the fix.
1.2.99, 2026-09-27
Runs open their dataset while they read X, so they finish sooner.
1.2.96, 2026-09-27
Small runs that go well skip run-report, so they cost less in Apify usage.
The run status now says why the run stopped, with its charged results &
targets.
Runs that stop on their input now name the diagnostics output in their status.
1.2.95, 2026-09-27
Runs that stop for missing or unusable input cost less in Apify usage.
1.2.91, 2026-09-27
Support now sees a finished run even while the service is busy.
Runs with a time limit keep a little more time to finish.
1.2.90, 2026-09-27
Runs with a time limit now stop in time & keep their results.
Large runs save their progress faster.
1.2.89, 2026-09-27
The run status now says where to find its diagnostics.
1.2.87, 2026-09-27
If the Actor cannot start, the run now ends with 1 free diagnostic.
Runs with hundreds of targets use less CPU.
1.2.86, 2026-09-26
Runs with a date range finish sooner.
A date range with no replies now ends empty, not as a partial run.
1.2.85, 2026-09-26
Runs now start collecting results sooner, so small runs finish faster.
1.2.84, 2026-09-26
Filling maxItems no longer logs errors for targets the run did not need.
A run that fills maxItems no longer reports a time limit.
1.2.83, 2026-09-26
Large runs use less memory.
1.2.82, 2026-09-26
Targets no longer fail when Xquik is busy. The Actor waits & tries again until
its time limit.
A page the service answers slowly in busy hours now arrives instead of timing
out.
1.2.81, 2026-09-26
Support can now see where each run spends its time.
1.2.80, 2026-09-26
Targets no longer fail when the service is busy. The Actor waits a few seconds
& tries again until its time limit.
1.2.77, 2026-09-25
Input & Output tab descriptions now say what each field does.
The README now focuses on what you get & how to run it.
Runs finish sooner when every reply to a post is already collected.
1.2.76, 2026-09-25
Support can now look up every finished run.
1.2.75, 2026-09-25
Runs with many posts or profiles finish faster.
1.2.74, 2026-09-25 update
Small reply threads finish much faster.
The status says how many replies X hides. It no longer asks for a rerun.
A run with a time window ends as complete once it reads that window.
1.2.74, 2026-09-25
Runs recover faster from temporary service delays.
A slow page now ends in time & keeps its rows.
1.2.73, 2026-09-25 update
A post that cannot be fully read keeps its rows & ends as partial.
Runs recover better from an empty answer.
Partial posts no longer count as failed targets or log errors.
Language filters now keep every matching reply.
1.2.73, 2026-09-23 update
The status now names every reason a run stopped early.
The diagnostic lists each cause in stopCauses, with advice.
1.2.73, 2026-09-20 update
Brief stalls on the first page no longer end a run as incomplete.
Large & old threads read much faster.
1.2.73, 2026-09-17
The status shows how much of a large thread X made available.
Runs end as complete once every reply in range is collected.
1.2.72, 2026-09-17
Runs report completion more accurately.
1.2.71, 2026-09-17
Runs finish sooner once every reply is collected.
Runs recognize posts that have no replies.
1.2.70, 2026-09-16
Find replies to posts inside larger conversations.
Unrelated conversation branches stay out of the results.