# X (Twitter) Replies Scraper | $0.00015/Reply | Pay-Per-Result (`xquik/x-reply-scraper`) Actor 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. - **URL**: https://apify.com/xquik/x-reply-scraper.md - **Developed by:** [Xquik](https://apify.com/xquik) (community) - **Categories:** Social media, Lead generation, Developer tools - **Features:** Limited permissions - **Stats:** 944 total users, 226 monthly users, 100.0% runs succeeded, 1 bookmarks - **User rating**: 5.00 out of 5 stars ## Pricing from $0.00015 / replies This Actor is paid per event and usage. You are charged both the fixed price for specific events and for Apify platform usage. Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have. Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event ## What's an Apify Actor? An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes. In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours, and optionally produces a well-defined JSON output, datasets with results, or files in key-value store. In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server. Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md. ## How to integrate an Actor? If asked about integration, you help developers integrate Actors into their projects. You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready. Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run. For examples already wired to this Actor's own input schema, see the [API](#api) section below. Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`). # README **English** · [Español](https://github.com/Xquik-dev/x-twitter-scraper/blob/master/apify/x-reply-scraper/README.es.md) · [Türkçe](https://github.com/Xquik-dev/x-twitter-scraper/blob/master/apify/x-reply-scraper/README.tr.md) · [简体中文](https://github.com/Xquik-dev/x-twitter-scraper/blob/master/apify/x-reply-scraper/README.zh-CN.md) · [日本語](https://github.com/Xquik-dev/x-twitter-scraper/blob/master/apify/x-reply-scraper/README.ja.md) · [한국어](https://github.com/Xquik-dev/x-twitter-scraper/blob/master/apify/x-reply-scraper/README.ko.md) · [Deutsch](https://github.com/Xquik-dev/x-twitter-scraper/blob/master/apify/x-reply-scraper/README.de.md) · [Français](https://github.com/Xquik-dev/x-twitter-scraper/blob/master/apify/x-reply-scraper/README.fr.md) · [Italiano](https://github.com/Xquik-dev/x-twitter-scraper/blob/master/apify/x-reply-scraper/README.it.md) [![Framer connects Xquik MCP to coding agents](https://img.youtube.com/vi/4UOSpoOoC3Y/maxresdefault.jpg)](https://youtu.be/4UOSpoOoC3Y?t=367)\ [Watch how Framer uses Xquik scrapers](https://youtu.be/4UOSpoOoC3Y?t=367) with Claude Code, Codex, Cursor & more, from 6:07. Xquik is the world's fastest & cheapest X (Twitter) scraper service with the most complete X data. Xquik's X (Twitter) Reply Scraper collects replies, comments & whole conversations. In public benchmarks, it reads replies 1.7x faster than 4 other Actors. It also costs the least per useful reply, as the [benchmark below](#benchmark) shows. Most other Apify Actors charge before filtering or deduplicating. Xquik charges only for **delivered, unique, filter-matching results**. Scrape Twitter replies & comments for **$0.00015 per delivered row** on every Apify plan, & read them without an X account. Paste post URLs, Tweet IDs, profile URLs or usernames. Export replies, conversations, authors, engagement, entities & media URLs. Apify bills your platform usage separately. You need no X account. Filters run before dataset writes, so you pay only for delivered rows. > Xquik is an independent third-party service. Not affiliated with X Corp. > "Twitter" and "X" are trademarks of X Corp. ### What does X (Twitter) Reply Scraper do? Xquik's X (Twitter) Reply Scraper collects public replies & comment conversations. It handles single posts, bulk URL lists, Tweet IDs & user reply timelines. #### Use cases - Measure sentiment & customer feedback under brand & product posts. - Rank the most liked replies & comments under a viral post. - Find leads who ask questions or name a need in public replies. - Review replies for moderation, spam & abuse. - Rebuild whole conversations for research & AI training datasets. - Track how an account replies to its customers over time. ### Why use X (Twitter) Reply Scraper? - **1.7x faster reply exports.** Its median run was 1.7x faster than the fastest of 4 other Actors. The [benchmark](#benchmark) ran on 2026-10-15. - **Lowest cost per useful reply.** It cost the least per useful reply in the [benchmark](#benchmark). - **2x the fields per reply.** Its median row had 100 fields in the [benchmark](#benchmark). That is 2x the median of the other Actors. - **Pick the conversation shape.** Keep direct replies, nested replies or both, down to the depth you set. `collectionStrategy` can also return the thread or only hidden replies. - **Rebuild every thread.** Each reply carries its parent in `inReplyToId`, its root in `rootTweetId` & its `depth`. - **Many posts in 1 run.** Paste post URLs, Tweet IDs, profiles & usernames together. A username returns that account's replies. - **Only the replies you want.** Filter by words, hashtags, author, language, verification, engagement, media & date. - **Sort by likes or date.** Rank replies by likes, or list the newest or oldest first. Rows come compact, full or rich, in `camelCase` or `snake_case`. - **Continue big threads later.** A run that stops early saves each target's place in `next-cursors`. Pass 1 as `startCursor` to continue. #### Complete results - Complete mode adds replies the author hid & explains empty threads. - Each answer holds the fullest data X has for it. #### Accurate rows - A post is called missing only when it's gone. - Reposts carry the full original text. - Every ID in a row stays exact. - Mentions, links, hashtags & highlights line up with the text. - A count that isn't known is listed in `unknownCounts`, never shown as 0. - Verified badges match what `x.com` shows. - Rows hold public data only. - Runs count the replies they didn't reach. - Ads & promoted entries never reach your rows. #### Fresh data - Reads keep working when X ships changes. #### Speed - One slow page doesn't hold up your run. - Actors read many handles, posts & queries at once. - Reads finish the moment their rows arrive. - Stalled Actor calls recover on their own. #### Fair billing - Bad input costs nothing & tells you what to fix. - Actors charge only for delivered, unique, matching rows. - A restarted run never charges twice. - Runs stay within your spend cap & still write their diagnostics. - Tweet, reply & follower run reports estimate what the run cost. - Small runs end with a tip that cuts cost. #### Reliability - A one-off error doesn't fail your run. - A deadline returns the rows already found, with diagnostics. - Actors ride out short Xquik outages. - Actor runs survive restarts without repeats. - One bad row doesn't sink a batch. - Stopped runs keep their rows & their report. - A run that can't start still explains itself. - Support can see exactly what a request or run returned. #### Built for agents - Actors accept input written for other Actors. - Output is ready for spreadsheets, with flat columns & engagement totals. - Scraper datasets describe every field. - Every run says why it ended & whether to retry. #### Rich data - Posts carry note text, edits, Community Notes, reach labels, reply controls & live events. - Rows carry source apps, media counts & professional account data. - Media comes with variants, alt text, sizes & availability reasons. #### Quality checks - Every field X shows is served, left out on purpose or proven absent. - Xquik tests every read live against X. ### What data can X (Twitter) Reply Scraper extract? The dataset & run-report schemas describe every returned field. Text, number & boolean fields also carry examples for agents & generated integrations. Every full reply row can include these core fields. | Field | Description | | ------------------- | ----------------------------------------------------- | | `id` | Reply ID | | `text` | Reply text | | `fullText` | Long-form reply text | | `createdAt` | Reply timestamp | | `lang` | X language code | | `url` | Direct reply URL | | `conversationId` | X conversation ID | | `inReplyToId` | Immediate parent ID | | `inReplyToUserId` | Parent author ID | | `inReplyToUsername` | Parent username | | `likeCount` | Likes | | `replyCount` | Child replies | | `retweetCount` | Reposts | | `quoteCount` | Quotes | | `viewCount` | Views | | `bookmarkCount` | Bookmarks | | `author` | Available public author metadata | | `media` | Images, videos, GIFs, and variants | | `entities` | Hashtags, cashtags, mentions, URLs & video timestamps | | `quoted_tweet` | Quoted post when available | | `retweeted_tweet` | Reposted post when available | Full rows also keep available source metadata. - Post type fields are `type`, `isReply`, `isQuoteStatus`, `isNoteTweet`, `isLimitedReply` & `isTranslatable`. - Text details are `displayTextRange`, `noteTweet`, `article`, `card` & `cashtagAttachments`. - Labels & notices are `contentDisclosure`, `communityNote`, `possiblySensitive`, `softIntervention`, `tombstone` & `exclusiveContent`. - Conversation details are `conversationControl`, `limitedActions`, `subscriberBadge` & `unmentionedUserIds`. - Context fields are `source`, `place`, `communityId`, `communityName`, `reactionContext`, `liveEventContext` & `postCta`. - Edit & availability fields are `edit`, `previousCounts`, `viewState` & `authorUnavailable`. Flat rows keep conversation ancestry, source details, result type & schema version. See OpenAPI for the exact fields. ### How do I use X (Twitter) Reply Scraper to scrape replies? New to Apify? [Create a free account](https://console.apify.com/sign-up?fpr=xquik) first. The free plan needs no credit card & gives $5 to spend each month. At $0.00015 per row, $5 pays for up to 33,000 rows before platform usage. Then come back here & press Try for free. 1. Paste post URLs, Tweet IDs, profile URLs or usernames. 2. Set `maxItems`, `scope` & the filters your job needs. 3. Run Xquik's X (Twitter) Reply Scraper & open the dataset. The form comes filled with a public conversation we tested. It returns up to 1,000 full, flat rows. Auto mode collects the full conversation by default. Deduplication & source attribution stay on. #### Scrape replies from a post URL ```json { "startUrls": [{ "url": "https://x.com/OpenAI/status/2082577277246972300" }], "maxItems": 100 } ``` #### Scrape replies from tweet IDs ```json { "tweetIds": ["2082577277246972300", "2083148725367783580"], "maxItemsPerTarget": 100, "maxItems": 10000 } ``` #### Collect the full nested conversation ```json { "tweetIds": ["2082577277246972300"], "collectionStrategy": "conversationSearch", "scope": "all", "maxDepth": 5, "sort": "oldest", "maxItems": 500 } ``` #### Scrape a user's reply timeline ```json { "usernames": ["OpenAI", "apify"], "maxItems": 10000 } ``` #### Filter replies before billing ```json { "tweetIds": ["2082577277246972300"], "anyWords": ["API", "agent", "developer"], "excludeWords": ["airdrop", "giveaway"], "lang": "en", "minLikes": 2, "minViews": 100, "verifiedOnly": true, "maxItems": 10000 } ``` #### Export flat CSV-friendly rows ```json { "tweetIds": ["2082577277246972300"], "outputMode": "full", "outputPreset": "flat", "fieldStyle": "camelCase", "maxItems": 100 } ``` ### Task examples Choose from 50 public tasks. Each has a bounded input & a matching dataset view. Edit any task before you run it. - [Scrape X post replies & Twitter comments](https://apify.com/xquik/x-reply-scraper/examples/scrape-post-replies) - [Scrape bulk Twitter replies](https://apify.com/xquik/x-reply-scraper/examples/scrape-bulk-post-replies) - [Rebuild a Twitter reply conversation](https://apify.com/xquik/x-reply-scraper/examples/rebuild-full-conversation) - [Rank Twitter replies by likes](https://apify.com/xquik/x-reply-scraper/examples/rank-most-liked-replies) - [Scrape latest Tweet replies](https://apify.com/xquik/x-reply-scraper/examples/collect-latest-replies) - [Remove spam from Twitter replies](https://apify.com/xquik/x-reply-scraper/examples/exclude-spam-keywords) - [Scrape English Twitter replies](https://apify.com/xquik/x-reply-scraper/examples/collect-english-replies) - [Scrape verified Twitter replies](https://apify.com/xquik/x-reply-scraper/examples/collect-verified-replies) - [Scrape Twitter replies with media](https://apify.com/xquik/x-reply-scraper/examples/collect-media-replies) - [Scrape a user's Twitter reply timeline](https://apify.com/xquik/x-reply-scraper/examples/scrape-profile-replies) - [Collect Twitter replies for AI agents](https://apify.com/xquik/x-reply-scraper/examples/collect-replies-for-ai-agents) - [Build an X reply RAG dataset](https://apify.com/xquik/x-reply-scraper/examples/build-x-reply-rag-dataset) - [Archive Twitter replies for LLMs](https://apify.com/xquik/x-reply-scraper/examples/archive-replies-for-llm-processing) - [Extract X reply leads for CRM](https://apify.com/xquik/x-reply-scraper/examples/extract-reply-leads-for-crm) ### How much does it cost to scrape X replies? Xquik's X (Twitter) Reply Scraper costs $0.00015 per delivered row on every Apify plan. Apify bills platform usage separately. For more volume, [pick an Apify plan](https://apify.com/pricing?fpr=xquik) with more prepaid usage. Xquik applies one charge per delivered data row. Replies that your filters or deduplication remove cost nothing. Diagnostic records in `diagnostics` are free. No start, URL, query, pagination or filter fee applies. ### Benchmark Xquik's X (Twitter) Reply Scraper & 4 other Actors read 200 replies to 1 post. That post is public & has 2,800+ replies. Xquik's median run was 1.7x faster than the fastest other Actor. It also cost the least per useful reply. Its median row had 100 fields, 2x the median of the others. A useful reply is unique & sits in that post's thread. - `xquik/x-reply-scraper` delivered 200 useful replies at $0.000156 per useful reply, 19.7 per second & 100 fields per row. [View run](https://console.apify.com/view/runs/nhLt4g4YMjck0a3EJ) - `xquik/x-reply-scraper` delivered 200 useful replies at $0.000156 per useful reply, 16.5 per second & 101 fields per row. [View run](https://console.apify.com/view/runs/d89hq348wWv3uXKbF) - `xquik/x-reply-scraper` delivered 200 useful replies at $0.000157 per useful reply, 14.4 per second & 101 fields per row. [View run](https://console.apify.com/view/runs/EviOWh0mfuQCmg5Qb) - `xquik/x-reply-scraper` delivered 200 useful replies at $0.000157 per useful reply, 13.6 per second & 101 fields per row. [View run](https://console.apify.com/view/runs/fcaxea2NSgv1bYBz5) - `xquik/x-reply-scraper` delivered 200 useful replies at $0.000156 per useful reply, 16.5 per second & 100 fields per row. [View run](https://console.apify.com/view/runs/ZPA7cXLo2Cjp5w1K4) - `xquik/x-reply-scraper` delivered 200 useful replies at $0.000157 per useful reply, 11.3 per second & 100 fields per row. [View run](https://console.apify.com/view/runs/W1WJthlB7HlUlsdn2) - `xquik/x-reply-scraper` delivered 200 useful replies at $0.000156 per useful reply, 20.1 per second & 100 fields per row. [View run](https://console.apify.com/view/runs/cjEy8ukBzYaMNPLEP) - `xquik/x-reply-scraper` delivered 200 useful replies at $0.000156 per useful reply, 20.6 per second & 100 fields per row. [View run](https://console.apify.com/view/runs/7KovOrh4gHEhmypa3) - `kaitoeasyapi/twitter-x-data-tweet-scraper-pay-per-result-cheapest` delivered 200 useful replies at $0.000220 per useful reply, 9.6 per second & 50 fields per row. [View run](https://console.apify.com/view/runs/ayhXrguBqIitOaHiQ) - `kaitoeasyapi/twitter-x-data-tweet-scraper-pay-per-result-cheapest` delivered 200 useful replies at $0.000220 per useful reply, 8.1 per second & 50 fields per row. [View run](https://console.apify.com/view/runs/dzdRog1lxaEysgPIO) - `scraper_one/x-post-replies-scraper` delivered 200 useful replies at $0.000263 per useful reply, 6.6 per second & 15 fields per row. [View run](https://console.apify.com/view/runs/sQOzCIlLD9zZxhOXi) - `api-ninja/x-twitter-replies-retweets-scraper` delivered 200 useful replies at $0.000400 per useful reply, 5.0 per second & 33 fields per row. [View run](https://console.apify.com/view/runs/Ld8JStCa5Nnhn6jAH) - `apidojo/tweet-scraper` delivered 199 useful replies at $0.000402 per useful reply, 6.7 per second & 51 fields per row. [View run](https://console.apify.com/view/runs/iwVzxxn5QL5hBsswR) All runs took place on 2026-10-15 on the Bronze tier. Cost is the customer's total spend per useful result. Ours includes the Apify usage our customers pay. Fields per row is the median count of non-empty fields. That count includes nested fields, & a list counts as 1. Open a run for its input, log & dataset. ### Empty, partial & stopped runs Xquik's X (Twitter) Reply Scraper explains empty, partial & stopped runs for free. The run status says why the run stopped. It also counts charged results & targets read. A run that reads every target & finds no reply writes no record. Its status says why & what to change. #### Incomplete extraction An interrupted run writes a free `partial` diagnostic. Available results stay intact. Read `availableResults`, `failedTargets`, `retryable` & `nextAction` before you retry. A successful Actor exit confirms delivery, not complete extraction. The status names every cause of an early stop. `stopCauses` lists each cause with its own `message`, `retryable` & `nextAction`. The causes are `target_not_found`, `target_failed`, `reply_reach` & `deadline_reached`. `reply_reach` means X served only part of a thread. A missing post or account does not count as a failure. The status names it, such as "X has no match for 1 target." It joins `stopCauses` only when another cause stopped the run. The run is `retryable` when any cause is. #### Diagnostics Successful data rows use `resultType: "reply"`. A run that needs attention writes exactly 1 free record to `diagnostics`. Examples are an invalid input, a skipped target or an early stop. The record says how to fix the problem. A run that reads every target & finds no reply writes none. Its status says why. The run status says why the run stopped. It also counts charged results & targets read. Runs with a problem always write `run-report`, including no-input and invalid-input exits. A large run writes it too. A small run that goes well skips it & saves Apify usage. Turn on `alwaysSaveRunRecords` to write it on every run. The report schema documents completion, billing, failures & saved cursors. Its `version` field reports the exact published Actor source version. The `status` field uses these values. - `no-input` - `invalid-input` - `replies-incomplete` - `zero-output` - `aborted` - `unexpected-error` ### Input The Input tab lists every option. Give at least 1 post URL, Tweet ID, profile URL or username. Every other field is optional. #### Reply targets & input aliases Use these primary fields. | Input | Purpose | | ------------- | ------------------------------------- | | `startUrls` | Mixed X post and profile URLs | | `tweetIds` | Numeric post IDs | | `usernames` | Profile reply timelines | | `startCursor` | Resume one target from a saved cursor | The input form shows canonical controls only. Compatibility aliases still work in JSON, API, SDK, automation & saved task inputs. When you combine canonical & alias fields, their existing resolution order applies. These aliases accept common field names from other scrapers. - URL aliases are `urls`, `tweetUrls`, `postUrls`, `profileUrls`, & `twitterUrl` as one string. - ID aliases are `conversationIds`, `postIds`, `ids`, `tweetId`, `id`. - Username aliases are `twitterHandles`, `screenname`. - Global limit aliases are `maxResults`, `max_results`, `resultsLimit`, `maxReplies`. - Per-target aliases are `maxRepliesPerTweet`, `maxCommentsPerPost`, `resultsPerCategory`. - The search alias is `useSearch`. - Nested reply aliases are `includeNestedReplies`, `includeRepliesOfReplies`. - The depth alias is `depth` as `1`, `2` or `3` for `maxDepth`. `full` sets no limit. - The scope alias is `onlyDirectReplies` for `scope: "direct"`. - Original post aliases are `includeOriginalTweet`, `includeSourceTweet`. With `includeSourceTweet`, `resultsPerCategory` caps the replies & the post is 1 more row. - The author alias is `excludeOpSelfReplies` for `excludeOriginalAuthor`. - Sort aliases are `sortBy` & `queryType` for `sort`. `top`, `newest` & `mostLiked` read as `relevance`, `latest` & `likes`. - Output aliases are `outputVariant`, `includeRaw`. `category` set to `replies` changes nothing. A category that is another Actor's job, such as `retweets` or `info`, stops the run. It reads & charges nothing. The message names the Actor to use. When you set one of these aliases & its canonical field, the canonical value wins. The run log names the alias that lost. Malformed or unsupported targets do not fail the Actor. When no valid target remains, the run writes a diagnostic with the fix. #### Coverage strategies Pick how the Actor collects replies. Auto fits most jobs. ##### Auto complete Use `collectionStrategy: "auto"` for most jobs. It collects every reply it can reach for your scope. Scope, depth, sort & author controls apply before your limits. It includes replies below non-root targets. When X hides part of a thread, the status says how many replies X hides. A `thread` run continues with `auto` when X's thread view ends before your limits. The other `collectionStrategy` values never switch modes. A coverage figure in diagnostics does not prove X has no more replies. Limits, missing data or errors can leave a run incomplete. ##### Direct replies Use `collectionStrategy: "replies"` for direct replies in X's own order. It supports saved cursors. ##### Conversation search Use `collectionStrategy: "conversationSearch"` for broad conversation coverage. ##### Full thread context Use `collectionStrategy: "thread"` to read the source conversation context. Set `includeOriginalPost: true` to keep the root post as depth 0. When X's thread view ends before `maxItems`, the run continues with `auto`. ##### Hidden replies The default `auto` strategy adds the replies the post's author hid. Each one is a row with `resultType: "hiddenReply"`, at the usual row price, & counts toward `maxItems`. A post without hidden replies costs nothing extra. Set `includeHiddenReplies: false` to leave them out. Use `collectionStrategy: "hiddenReplies"` for the hidden replies alone. X lists them oldest first, with the replies to them. A post without hidden replies returns no rows. #### Direct & nested reply controls Use `scope` to choose the result shape. | Value | Result | | -------- | -------------------------------------------- | | `direct` | Keep depth 1 replies | | `nested` | Keep replies to replies at depth 2+ | | `all` | Keep every available direct and nested reply | Use `maxDepth` to limit nesting. When X omits a conversation ancestor, the parent link can be missing. The Actor preserves the best available depth. #### Sorting Use `sort` with these values. - `relevance` keeps X source order - `latest` sorts newest first - `oldest` sorts oldest first - `likes` sorts highest like count first `likes` runs can miss some replies. Profile targets collect your requested count of unique, filtered results, then sort them. Tweet targets keep global sorting. The `sortBy` & `queryType` compatibility aliases still work. #### Reply filters All supported filters run before dataset writes. ##### Text & entity filters | Input | Behavior | | ---------------- | --------------------------------- | | `exactPhrase` | Require one exact phrase | | `anyWords` | Require at least 1 word or phrase | | `excludeWords` | Remove matching words or phrases | | `keywordInclude` | Alias merged with `anyWords` | | `keywordExclude` | Alias merged with `excludeWords` | | `hashtags` | Require at least 1 hashtag | | `cashtags` | Require at least 1 cashtag | | `mentioning` | Require an @mention | ##### Author & language filters | Input | Behavior | | ----------------------- | -------------------------------------- | | `fromUser` | Keep one reply author | | `toUser` | Keep replies addressed to one username | | `lang` | Keep one X language code | | `verifiedOnly` | Require any public verification signal | | `blueVerifiedOnly` | Require X Premium verification | | `excludeOriginalAuthor` | Remove source-author self-replies | ##### Engagement filters Use `minLikes`, `minReplies`, `minRetweets`, `minQuotes`, `minViews` & `minBookmarks`. The `minFaves` alias maps to `minLikes`. ##### Media & time filters - Set `hasMediaOnly: true` for replies with public media. - Set `mediaType` to `any`, `image`, `video`, `gif` or `link`. - Set `mediaType` to `none` for text replies without media or links. - Set `since` for an inclusive start timestamp. - Set `until` for an exclusive end timestamp. - Use `sinceTime` & `untilTime` as compatibility aliases. ### Output Each reply row is a JSON object. The dataset & run-report schemas describe every field, so AI agents can read rows without guessing. Export the dataset as JSON, CSV, Excel or HTML. #### Author metadata Nested authors follow the public profile contract. It covers identity, counts, verification, availability, professional data & profile biographies. Flat output adds `authorId`, `authorUsername`, `authorName`, `authorFollowers`, `authorFollowing` & `authorVerified`. #### Media metadata Media covers availability, geometry, tags & video variants. It also has the `watchNowUrl` & `visitSiteUrl` actions. Flat output adds `mediaUrls`. #### Output example A trimmed reply row looks like this. ```json { "resultType": "reply", "id": "1881423000000000000", "url": "https://x.com/example/status/1881423000000000000", "text": "Thanks for sharing this update.", "createdAt": "2026-08-09T12:00:00.000Z", "lang": "en", "conversationId": "1881422000000000000", "rootTweetId": "1881422000000000000", "parentReplyId": "1881422000000000000", "depth": 1, "isDirectReply": true, "likeCount": 42, "replyCount": 3, "retweetCount": 5, "quoteCount": 2, "viewCount": 1000, "bookmarkCount": 7, "authorUsername": "example", "authorName": "Example User", "authorFollowers": 1000, "authorVerified": false, "mediaUrls": ["https://pbs.twimg.com/media/example.jpg"], "sourceTweetId": "1881422000000000000", "sourceTarget": "1881422000000000000" } ``` Sample values are illustrative. Real runs return live data. #### Output modes Pick how wide each dataset row is. ##### Compact Set `outputMode: "compact"` for a narrower dataset. It keeps text, conversation, author, engagement & media fields. ##### Full Set `outputMode: "full"` to keep every supported public field. ##### Rich Set `outputMode: "rich"` for the most data per row. Rich rows keep every full column & add `hasCommunityNotes`, `quotedTweetPermalink`, `unavailableAuthorId` & media `sourceUser` at the end. ##### Raw Set `outputMode: "raw"` to add a sanitized source snapshot under `raw`. ##### Nested or flat The default `flat` layout keeps nested objects & adds author fields for tables. Set `outputPreset: "nested"` to omit the added flat fields. ##### Field naming Set `fieldStyle` to `source`, `camelCase` or `snake_case`. The Actor avoids overwriting colliding source keys. ### Output columns 8 inputs shape each row after the run reads it. They run no code & change no price. | Field | What it does | | ------------------- | ----------------------------------------------------------- | | `fields` | Keep only these fields, in the order & spelling you write | | `omitFields` | Drop these fields & keep the rest | | `renameFields` | Move a field to a column with a new name | | `flatten` | Turn each nested object into top-level columns | | `fillMissingFields` | Fill a kept field a row lacks with `null`. On by default | | `joinFields` | Turn each of these lists into 1 text value | | `joinSeparator` | Text between joined items. The default is a comma & a space | | `constantFields` | Add a column with the same text on every row | - Use a dot for a field inside an object, such as `author.id`. Case & underscores do not matter. - Every row keeps its `id`. - With `fields`, a field a row lacks arrives as `null`. Every row then has the same columns. - A wrong field name stops the run before it reads & charges nothing. - If names cannot be checked, the run reads on & lists unseen names last. - The run ignores a map function or jq filter written for another Actor. Name a computed column in `fields` or `renameFields` to add it. | Column | Formula | | ------------------- | ---------------------------------------------------------------------------------- | | `totalEngagement` | `likeCount` + `replyCount` + `retweetCount` + `quoteCount`. A missing count adds 0 | | `engagementRate` | `totalEngagement` × 100 ÷ the author's `followers`, to 4 decimals | | `engagementPerView` | `totalEngagement` × 100 ÷ `viewCount`, to 4 decimals | `totalEngagement` is `null` for a row without those counts. A rate is `null` when its divisor is missing or 0. ### Run options #### Limits, billing & continuation `maxItems` limits delivered rows across the run. `maxItemsPerTarget` limits each post or profile. One run can read many targets. Caps, deduplication, attribution & billing stay exact across them. The Actor removes duplicate rows before output & billing. Set `dedupeAcrossTargets: false` to keep duplicate rows from different targets. After a run stops at its time limit, read `next-cursors` from the default key-value store. Pass one cursor through `startCursor` to continue that target. ##### Apify timeout The default Apify timeout is `0`, so runs have no time limit. The Actor continues until it reaches the cap or runs out of eligible data. You can still set a finite Apify timeout. Then `completionReason: "deadline_reached"` means that limit is near. The Actor saves replies & the report, then exits cleanly before the limit. Delivered replies bill once. Unfinished targets stay resumable. #### API examples Each example runs Xquik's X (Twitter) Reply Scraper & returns the dataset items. Replace `` with your Apify API token. ##### JavaScript ```javascript import { ApifyClient } from 'apify-client'; const client = new ApifyClient({ token: '' }); const run = await client .actor('xquik/x-reply-scraper') .call({ tweetIds: ['2082577277246972300'], collectionStrategy: 'auto', scope: 'all', maxItems: 100, }); const { items } = await client.dataset(run.defaultDatasetId).listItems(); console.log(items); ``` ##### Python ```python from apify_client import ApifyClient client = ApifyClient("") run = client.actor("xquik/x-reply-scraper").call(run_input={ "tweetIds": ["2082577277246972300"], "collectionStrategy": "auto", "scope": "all", "maxItems": 100, }) for item in client.dataset(run["defaultDatasetId"]).iterate_items(): print(item) ``` ##### cURL ```bash actor=xquik~x-reply-scraper curl "https://api.apify.com/v2/acts/$actor/run-sync-get-dataset-items" \ -X POST \ -H "Authorization: Bearer " \ -H "Content-Type: application/json" \ -d '{"tweetIds":["2082577277246972300"],"maxItems":100}' ``` #### Automation & integrations Run Xquik's X (Twitter) Reply Scraper through Apify schedules, webhooks or API clients. Connect it to Make, Zapier, n8n, Google Sheets or cloud storage. Agents can call it through the [Apify MCP server](https://docs.apify.com/platform/integrations/mcp). Eligible agent workflows can also use [x402](https://docs.apify.com/integrations/x402) or [Skyfire](https://docs.apify.com/integrations/skyfire). Xquik also offers 86 dashboard tools, a REST API, signed webhooks & an MCP server. #### AI agent & MCP readiness Run Xquik's X (Twitter) Reply Scraper through Apify MCP, API clients, x402 or Skyfire. - Limited permissions protect unrelated Apify account data. - Pay-per-event billing ties cost to delivered results. - Standby mode stays off for compatibility with agentic payments. - Typed schemas describe replies, run reports & continuation cursors. - Bounded defaults prevent accidental unbounded agent runs. - Stable `camelCase` & `snake_case` modes simplify tool chaining. - Diagnostic rows include a status, a message & a recovery action. - Run reports include exact outcomes, stop reasons & charge estimates. #### Always use the latest build Select `latest` for every run to get all published fixes. If you specify no build, Apify uses this Actor's `latest` default. Console runs & standard API examples inherit that default. Saved tasks may override the Actor default. Schedules & task integrations reuse that choice. Keep every override set to `latest`. Apify does not redirect exact build numbers to `latest`. Replace pinned numbers with `latest`. Use exact builds only for temporary rollbacks. ### Related Xquik Actors Every Xquik Actor shares the same extraction engine, filter-first billing & diagnostics. Pick the one that matches the data you need. - [X (Twitter) Tweet Scraper](https://apify.com/xquik/x-tweet-scraper) scrapes tweets from searches, profile timelines, Lists & tweet IDs with 50+ filters & flat exports. Use it when you need tweet data without analysis. From $0.00015 per row. - [X (Twitter) Profile Scraper](https://apify.com/xquik/x-profile-scraper) scrapes profiles plus their posts, replies, media & followers from handles, IDs or URLs. Use it when you start from accounts rather than searches. From $0.00015 per row. - [X (Twitter) Engagement Scraper](https://apify.com/xquik/x-engagement-scraper) scrapes replies, quotes, retweeters & threads for post URLs or IDs in bulk. Use it when you measure who engaged with posts. From $0.00015 per row. - [X (Twitter) Quote Tweets Scraper](https://apify.com/xquik/x-quote-tweets-scraper) scrapes the quote tweets of posts with text, media, counts, authors & 11 filters. Use it when you study who quoted posts & what they said. From $0.00015 per tweet. - [X (Twitter) Follower Scraper](https://apify.com/xquik/x-follower-scraper) scrapes followers, following, List members, subscribers & Community members as profile rows. Use it when you need audience or member lists. From $0.00015 per profile. - [X (Twitter) User Search Scraper](https://apify.com/xquik/x-user-search-scraper) searches users by handle, bio & location with follower, verification, age & location filters. Use it when you build account lists from search. From $0.00015 per profile. - [X (Twitter) Account Location Scraper](https://apify.com/xquik/x-account-location-scraper) checks where accounts are based with X's "Account based in" label, "connected via" & username changes. Use it when you vet where accounts are based. From $0.00015 per account. - [X (Twitter) Email Scraper](https://apify.com/xquik/x-email-scraper) gets the emails, phones & links accounts publish on their profiles, from handles, followers or user searches. Use it when you need the emails profiles publish. From $0.00015 per profile. - [X (Twitter) List Scraper](https://apify.com/xquik/x-list-scraper) scrapes List posts, members & followers from List URLs or IDs. Use it when a curated List defines your sources. From $0.00015 per row. - [X (Twitter) Community Scraper](https://apify.com/xquik/x-community-scraper) scrapes Community info, posts, searches, members & moderators. Use it when your sources are X Communities. From $0.00015 per row. - [X (Twitter) Space Scraper](https://apify.com/xquik/x-space-scraper) finds Spaces by keyword & reads their titles, states, times, listener counts, hosts & speakers. It also reads broadcasts by URL or ID. Use it when you track live audio & video on X. From $0.00015 per Space or broadcast. - [X (Twitter) Trends Scraper](https://apify.com/xquik/x-trends-scraper) scrapes real-time trends by location with rank, volume, query & WOEID. Use it when you track what is trending where. From $0.00015 per trend. - [X (Twitter) Jobs Scraper](https://apify.com/xquik/x-job-scraper) scrapes X job listings by keyword, place, workplace, seniority & company, with salaries & apply links. Use it when you collect job openings posted on X. From $0.00015 per job. - [X (Twitter) Article Scraper](https://apify.com/xquik/x-article-scraper) scrapes long-form X Articles as Markdown & text with covers, authors, dates & metrics. Use it when you need article bodies, not tweets. From $0.00015 per article. - [X (Twitter) Media Downloader](https://apify.com/xquik/x-media-downloader) extracts or stores photos, videos & GIFs from posts or profiles with MP4 & metadata options. Use it when you need the media files themselves. From $0.00015 per media row. - [X (Twitter) Brand Monitoring with AI Analysis](https://apify.com/xquik/x-twitter-brand-monitoring) tracks brand mentions with AI relevance, sentiment & customer-experience answers & compares runs. Use it when you watch a brand over time. From $0.0003 per analyzed tweet. - [X (Twitter) Tweet Sentiment Analysis with AI](https://apify.com/xquik/x-tweet-sentiment-analysis) labels attitude, intensity & sarcasm probability for every tweet with AI. Use it when you need general sentiment on any topic. From $0.0003 per analyzed tweet. - [X (Twitter) Stock & Crypto AI Trading Signals](https://apify.com/xquik/x-twitter-stock-crypto-signals) labels bullish, bearish, neutral or mixed stance, content type, conviction & asset relevance with AI. Use it when you follow stocks, crypto or trading talk. From $0.0003 per analyzed tweet. - [X (Twitter) News Monitor with AI Analysis](https://apify.com/xquik/x-twitter-news-monitor) labels news posts by format, source attribution & topic relevance with AI. Use it when you separate reporting from commentary. From $0.0003 per analyzed tweet. - [X (Twitter) Tweet Classifier with AI Analysis](https://apify.com/xquik/x-twitter-tweet-classifier) answers your own category, score & yes/no questions for every tweet with AI. Use it when the preset analyses do not fit your labels. From $0.0003 per analyzed tweet. - [X (Twitter) Tweet Viral Score Analyzer with AI](https://apify.com/xquik/x-tweet-viral-score-analyzer) estimates a Viral Score from 0 to 100 & a verdict for every tweet from 8 AI trait answers. Use it when you study why tweets spread or flop. From $0.0003 per analyzed tweet. - [X (Twitter) Monitor](https://apify.com/xquik/x-twitter-monitor) catches every new tweet, reply, quote, repost & profile change of accounts, usually in under a second after X shows it, plus keyword tweets & follows. Use it when you need alerts as soon as X shows a tweet. From $0.0045 per monitor-hour. - [X (Twitter) to Discord Bot](https://apify.com/xquik/x-twitter-to-discord) sends every new tweet, reply, quote & repost of accounts to a Discord channel through its webhook, with no bot to host. Use it when you want an account's tweets in a Discord channel. From $0.0045 per monitor-hour. - [X (Twitter) Crypto Tracker](https://apify.com/xquik/x-twitter-crypto-tracker) tracks the tweets, deleted tweets, profile changes & follows of crypto accounts & KOLs, plus cashtag tweets. Use it when you act on what crypto accounts post or follow. From $0.0045 per monitor-hour. - [X (Twitter) Follower Tracker](https://apify.com/xquik/x-twitter-follower-tracker) tracks the new & lost followers of an account, & whom it follows or unfollows, with each account's full profile. Use it when you read an account's followers or follows as a signal. From $0.0045 per monitor-hour. - [X (Twitter) Post Tracker](https://apify.com/xquik/x-twitter-post-tracker) records the views, likes, reposts, replies, quotes & bookmarks of chosen posts on each run, with the change since the last run. Use it when you track how posts perform over time. From $0.00015 per snapshot. ### FAQ Answers to common questions, then where to get help. #### How do I scrape the comments on a tweet? Paste the post URL into `startUrls` & click Start. X calls comments replies, so each comment is 1 reply row. #### Can I scrape replies from many tweets at once? Yes. Paste many post URLs or Tweet IDs in 1 run. Each reply keeps the source post in `sourceTarget`. #### Does it include nested replies? Yes. The default `scope` collects direct & nested replies. Set `scope` to `direct` for replies to the post only. `maxDepth` limits how deep a run goes. #### Does it get replies the author hid? Yes. The default `auto` strategy adds them as `hiddenReply` rows. Set `includeHiddenReplies: false` to skip them. #### Can I sort replies by likes or date? Yes. Set `sort` to rank replies by likes, or to list the latest or oldest first. #### Can I export replies to CSV or Excel? Yes. Export the dataset as CSV, Excel, JSON or HTML. Flat output keeps 1 reply per row with author fields beside it. #### Can I scrape a user's replies instead of a post's? Yes. Paste a profile URL or a username. The run reads that user's reply timeline. #### Do I need an X account or an X API key? No. You need no X account or X API key. Paste a post link & the run reads its public replies. #### Is it legal to scrape X replies? Xquik's X (Twitter) Reply Scraper collects public replies & does not bypass protected accounts. Collect only public data. Follow applicable laws & platform rules. Reply datasets can contain personal data. Choose a lawful purpose. Minimize retention. Protect exports. Honor deletion & access requests where required. Ask qualified counsel when uncertain. #### Why did my run return fewer replies than the post shows? When X hides part of a thread, the status says how many replies X hides. If a run stops early, its status says how many replies it didn't reach. X's reply count for the post sets the total. When a date sort may skip replies between rows, the status says so. `reply_reach` in `stopCauses` means X served only part of a thread. Filters, deduplication, `scope`, `maxDepth` & your limits also lower the count. #### Can I use the API, schedules & integrations? Yes. The [API tab](https://apify.com/xquik/x-reply-scraper/api) shows Python, JavaScript & cURL examples. Use Apify [schedules](https://docs.apify.com/platform/schedules) to run Xquik's X (Twitter) Reply Scraper on a cron. It also connects to Make, Zapier, n8n & Google Sheets. #### Where do I get help? Open an issue in the [Issues tab](https://apify.com/xquik/x-reply-scraper/issues) with the run ID. #### Can I get a custom solution? Yes. Describe what you need in the [Issues tab](https://apify.com/xquik/x-reply-scraper/issues). Xquik also offers a dashboard, a REST API, an MCP server & webhooks. Find Xquik's website on its [Apify profile](https://apify.com/xquik). # Changelog This Actor's version history is a separate document: https://apify.com/xquik/x-reply-scraper/changelog.md # Actor input Schema ## `startUrls` (type: `array`): Public x.com or twitter.com post and profile URLs. Mix both in one run. The field accepts strings and {"url":"..."} objects. ## `tweetIds` (type: `array`): Numeric Tweet IDs. Each ID becomes a reply-conversation target. ## `usernames` (type: `array`): X usernames with or without @. Each one returns that account's public With Replies timeline. ## `maxItems` (type: `integer`): Global reply-row limit across every target. The form starts at 1,000. A run can return 100,000 rows & more, so raise it for a full export. ## `maxItemsPerTarget` (type: `integer`): Optional delivered-row cap for each post or profile target. ## `scope` (type: `string`): direct keeps replies to the source post. nested keeps replies to replies. all keeps every available conversation reply. ## `maxDepth` (type: `integer`): Maximum parent-child depth from the source post. 1 keeps direct replies. Leave empty for every available depth. ## `sort` (type: `string`): Keep X relevance order, or sort the collected result by latest, oldest, or most liked. ## `includeOriginalPost` (type: `boolean`): Add the source post as depth 0 when available. ## `includeHiddenReplies` (type: `boolean`): Add the replies the post author hid, as hiddenReply rows. Each costs 1 result. Turn it off to skip them. ## `exactPhrase` (type: `string`): Keep replies containing this exact phrase. Case-insensitive. ## `anyWords` (type: `array`): Keep replies containing at least 1 listed word or phrase. ## `excludeWords` (type: `array`): Remove replies containing any listed word or phrase. ## `hashtags` (type: `array`): Keep replies containing at least 1 listed hashtag. Values may include #. ## `cashtags` (type: `array`): Keep replies containing at least 1 listed cashtag. Values may include $. ## `fromUser` (type: `string`): Keep replies written by this username. ## `toUser` (type: `string`): Keep replies whose reply target is this username. ## `mentioning` (type: `string`): Keep replies mentioning this username. ## `lang` (type: `string`): Keep an X language code such as en, es, tr, de, or ja. ## `excludeOriginalAuthor` (type: `boolean`): Remove self-replies from the source-post author when author data is available. ## `verifiedOnly` (type: `boolean`): Keep replies from accounts with any public verification signal. ## `blueVerifiedOnly` (type: `boolean`): Keep replies from X Premium or Blue verified accounts. ## `since` (type: `string`): Inclusive date or timestamp, such as 2026-07-01 or an ISO 8601 timestamp. ## `until` (type: `string`): Exclusive date or timestamp, such as 2026-08-01 or an ISO 8601 timestamp. ## `minLikes` (type: `integer`): Minimum like count per delivered reply. ## `minReplies` (type: `integer`): Minimum reply count on each delivered reply. ## `minRetweets` (type: `integer`): Minimum repost count per delivered reply. ## `minQuotes` (type: `integer`): Minimum quote count per delivered reply. ## `minViews` (type: `integer`): Minimum view count per delivered reply. ## `minBookmarks` (type: `integer`): Minimum bookmark count per delivered reply. ## `hasMediaOnly` (type: `boolean`): Keep replies with an image, video, or GIF attachment. ## `mediaType` (type: `string`): Keep replies containing any media, an image, video, GIF, or link. Text only keeps replies without media or links. ## `outputMode` (type: `string`): compact keeps fields used for analysis. full preserves every supported public reply field. rich adds every other public field X provides. raw also adds the sanitized source row. ## `outputPreset` (type: `string`): nested preserves author and media objects. flat adds top-level author fields and media URL arrays for CSV and spreadsheets. ## `fieldStyle` (type: `string`): Preserve source names or normalize nested output to camelCase or snake_case. ## `includeTargetMetadata` (type: `boolean`): Add sourceTweetId, sourceTarget, and sourceUrl fields to every delivered row. ## `collectionStrategy` (type: `string`): auto picks the best way to collect the chosen scope. conversationSearch favors broad conversation coverage. replies returns direct replies in X order. thread reads the full conversation context. hiddenReplies returns the replies the post author hid. ## `startCursor` (type: `string`): Resume one target from a saved opaque cursor. Pass it unchanged. Legacy cursors remain supported. Use separate runs per cursor. ## `dedupeAcrossTargets` (type: `boolean`): Write the first occurrence when the same reply appears under multiple targets. ## `alwaysSaveRunRecords` (type: `boolean`): Save run-report on every run. When off, small runs that go well skip it & cost less. ## `urls` (type: `array`): Alias for Start URLs. Accepts URL strings or {"url":"..."} objects. ## `tweetUrls` (type: `array`): Tweet or post URL alias. ## `postUrls` (type: `array`): Post URL alias. ## `profileUrls` (type: `array`): Alias for Usernames. Add profile URLs whose reply timelines to collect. ## `conversationIds` (type: `array`): Alias for Tweet IDs. ## `postIds` (type: `array`): Alias for Tweet IDs. ## `ids` (type: `array`): Alias for Tweet IDs. ## `tweetId` (type: `string`): Single Tweet ID alias. ## `id` (type: `string`): Single Tweet ID alias. ## `twitterHandles` (type: `array`): Alias for Usernames. ## `screenname` (type: `string`): Single profile-reply username alias. ## `useSearch` (type: `boolean`): Compatibility alias. true selects conversationSearch. ## `includeNestedReplies` (type: `boolean`): Compatibility alias for Reply Scope. Explicit Reply Scope takes precedence. ## `includeRepliesOfReplies` (type: `boolean`): Compatibility alias for Reply Scope. Explicit Reply Scope takes precedence. ## `maxResults` (type: `integer`): Alias for Maximum Delivered Rows. ## `max_results` (type: `integer`): Alias for Maximum Delivered Rows. ## `resultsLimit` (type: `integer`): Alias for Maximum Delivered Rows. ## `maxReplies` (type: `integer`): Alias for Maximum Delivered Rows. ## `maxRepliesPerTweet` (type: `integer`): Alias for Maximum Rows per Target. ## `maxCommentsPerPost` (type: `integer`): Compatibility alias for Maximum Rows per Target. ## `queryType` (type: `string`): Compatibility alias. Latest selects latest. Likes selects most liked. Other values keep relevance. ## `sortBy` (type: `string`): Alias for Sort Replies. ## `includeOriginalTweet` (type: `boolean`): Alias for Include Original Post. ## `keywordInclude` (type: `array`): Alias merged with Any Included Words. ## `keywordExclude` (type: `array`): Alias merged with Excluded Words. ## `language` (type: `string`): Alias for Reply Language. ## `minFaves` (type: `integer`): Alias for Minimum Likes. ## `sinceTime` (type: `string`): Alias for Replies Since. ## `untilTime` (type: `string`): Alias for Replies Until. ## `outputVariant` (type: `string`): Alias for Output Detail. ## `includeRaw` (type: `boolean`): Compatibility alias. true selects raw output. ## `fields` (type: `array`): Keep only these fields in each row. Pick names or type your own. Use a dot for a field inside an object, such as author.id. Columns arrive in the order & spelling you write. Every row keeps its id. Leave empty for every field. The price per row stays the same. A wrong name stops the run before it reads, at no charge. If names cannot be checked, the run reads on & lists unseen names last. ## `omitFields` (type: `array`): Drop these fields & keep the rest. Every row keeps its id. ## `renameFields` (type: `array`): Give a field a new column name. The key is the field. The value is the new name. A renamed field becomes a top-level column. ## `flatten` (type: `boolean`): Turn each nested object into top-level columns, such as authorId. Lists stay lists. Use it for CSV & spreadsheets. ## `fillMissingFields` (type: `boolean`): With Fields to keep, a field a row lacks arrives as null. Every row then has the same columns. Turn it off to leave such fields out. ## `joinFields` (type: `array`): Turn each of these lists into 1 text value. Use it for CSV cells. ## `joinSeparator` (type: `string`): Text between the items of a joined list. ## `constantFields` (type: `array`): Add a column with the same text on every row. The key is the column name, such as campaign. The value is its text. ## Actor input object example ```json { "startUrls": [ { "url": "https://x.com/OpenAI/status/2082577277246972300" } ], "tweetIds": [ "2082577277246972300" ], "usernames": [ "OpenAI", "@apify" ], "maxItems": 1000, "scope": "all", "sort": "relevance", "includeOriginalPost": false, "includeHiddenReplies": true, "excludeOriginalAuthor": false, "verifiedOnly": false, "blueVerifiedOnly": false, "hasMediaOnly": false, "outputMode": "full", "outputPreset": "flat", "fieldStyle": "source", "includeTargetMetadata": true, "collectionStrategy": "auto", "dedupeAcrossTargets": true, "alwaysSaveRunRecords": false, "useSearch": false, "includeOriginalTweet": false, "includeRaw": false, "flatten": false, "fillMissingFields": true, "joinSeparator": ", " } ``` # Actor output Schema ## `replies` (type: `string`): Read replies with stable resultType values, original-post markers, conversation metadata, authors, engagement, media, and source attribution. ## `diagnostics` (type: `string`): Free actionable diagnostics, written only when something needs attention. They cover partial, invalid, aborted & recovered runs. An empty run whose filters removed replies writes 1 too. A run that read every target & found no reply writes none. A partial diagnostic lists each stop cause in stopCauses. Real replies remain in the dataset. ## `runReport` (type: `string`): Inspect the typed outcome, completion reason, target stop reasons, counts, charge, and anomaly totals. An incomplete read reports pagination_safety_limit. A run writes it when it hits a problem, is large or has Always save run records on. Small runs that go well skip it & state the outcome in their status. ## `continuationCursors` (type: `string`): Read saved cursors for targets that a limit stopped. Pass each cursor back unchanged. # API You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup. ## JavaScript example ```javascript import { ApifyClient } from 'apify-client'; // Initialize the ApifyClient with your Apify API token // Replace the '' with your token const client = new ApifyClient({ token: '', }); // Prepare Actor input const input = { "startUrls": [ { "url": "https://x.com/OpenAI/status/2082577277246972300" } ], "maxItems": 1000 }; // Run the Actor and wait for it to finish const run = await client.actor("xquik/x-reply-scraper").call(input); // Fetch and print Actor results from the run's dataset (if any) console.log('Results from dataset'); console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`); const { items } = await client.dataset(run.defaultDatasetId).listItems(); items.forEach((item) => { console.dir(item); }); // 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs ``` ## Python example ```python from apify_client import ApifyClient # Initialize the ApifyClient with your Apify API token # Replace '' with your token. client = ApifyClient("") # Prepare the Actor input run_input = { "startUrls": [{ "url": "https://x.com/OpenAI/status/2082577277246972300" }], "maxItems": 1000, } # Run the Actor and wait for it to finish run = client.actor("xquik/x-reply-scraper").call(run_input=run_input) # Fetch and print Actor results from the run's dataset (if there are any) print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}") for item in client.dataset(run.default_dataset_id).iterate_items(): print(item) # 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start ``` ## CLI example ```bash echo '{ "startUrls": [ { "url": "https://x.com/OpenAI/status/2082577277246972300" } ], "maxItems": 1000 }' | apify call xquik/x-reply-scraper --silent --output-dataset ``` ## MCP server setup ```json { "mcpServers": { "apify": { "type": "http", "url": "https://mcp.apify.com/?tools=fetch-actor-details,xquik/x-reply-scraper" } } } ``` The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer ` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations). ## OpenAPI specification Download the OpenAPI definition: https://api.apify.com/v2/actors/Ss97VOmxYmtGJCg6e/builds/mVNoOeekidkb1EXSD/openapi.json