X (Twitter) Conversation & Replies Scraper

Fetch a public X post and its reply conversation through the official X API v2. Export normalized thread data for customer research, sentiment workflows, community analysis, support monitoring, and downstream agents.

What this Actor does

• Accepts X post URLs or numeric post IDs.
• Fetches the root post.
• Searches public replies belonging to the same conversation.
• Preserves reply-parent IDs and conversation IDs when the API exposes them.
• Supports configurable reply caps, thread-depth handling, quote inclusion, and minimum engagement.
• Normalizes authors, timestamps, engagement metrics, and thread relationships.
• Uses your own X Developer Bearer Token.

Bring your own X API token

Live X access uses a BYOT (bring your own token) model.

Enter your X Developer Bearer Token in the bearerToken field. Apify encrypts this secret input before storing the run input.

Important:

• X API usage is billed by X to the developer account that issued the token.
• Store users never use a NexaScout X credential.
• The Actor does not fall back to an owner-level X token.
• Live requests are locked to the official X API host.
• The token is not written to output.

Quick start

Replace the example post URL with the conversation you want to analyze:

{
  "posts": [
    "https://x.com/USERNAME/status/POST_ID"
  ],
  "bearerToken": "YOUR_X_BEARER_TOKEN",
  "searchMode": "recent",
  "maxRepliesPerPost": 25,
  "maxDepth": 3,
  "includeRoot": true,
  "includeQuotes": false
}

Main inputs

posts

One or more X post URLs or numeric post IDs.

bearerToken

Your X Developer Bearer Token. Required for live X collection.

searchMode

• recent — uses X recent search for reply discovery.
• all — requests full-archive search. Your X developer project must have access to that endpoint.

Thread controls

• maxRepliesPerPost — maximum replies emitted per root post.
• maxDepth — maximum known thread depth to keep where depth is derivable.
• includeRoot — include the root post in output.
• includeQuotes — include quote posts where supported.
• minEngagement — filter low-engagement replies.

Output

Each dataset row is a normalized root post or reply. Common fields include:

• postId
• url
• author fields
• text
• createdAt
• engagement metrics
• conversationId
• inReplyToId
• threadDepth
• quote/retweet indicators

The run also stores a RUN_SUMMARY record with processed roots, emitted items, retries, failures, and warnings.

Good use cases

• Customer feedback threads
• Product launch reactions
• Support and feature-request discussions
• Brand mention conversations
• Viral post reply analysis
• Evidence collection for market research
• Feeding normalized conversations into sentiment or classification workflows

Pricing

Apify Store charges for this Actor are separate from X API charges.

Your X Developer account is responsible for X API usage generated by your token. Check current X API pricing and limits before large conversation runs.

Limitations

• Reply discovery is limited to data returned by the official X API.
• Older conversations may require full-archive search access.
• Thread depth is not guessed when the API does not expose enough parent information.
• Protected, deleted, unavailable, or otherwise inaccessible content is not returned.
• X rate limits and product limits apply.

This Actor is not affiliated with X Corp.