X Profile Tweets Scraper

Export tweets visible in public X profile-page or supplied status-page responses. Keep text, source identifiers, exposed engagement counts, media references, reply flags and observation times for your own research. This is a public-page sample rather than an authenticated full archive, and it does not log in or access protected posts.

Quick start

Start with one known public profile and a small per-profile cap. The existing Apify input is:

{
  "profileUrls": [
    { "url": "https://x.com/Apify" }
  ],
  "statusUrls": [],
  "maxTweetsPerProfile": 10,
  "includeReplies": true,
  "connectionMode": "automatic"
}

Prefer a video guide? This short Apify walkthrough shows you how to set up and run an Actor. It uses a different Actor, but the setup steps are the same.

Ready-to-run examples

Use these saved Store examples as starting points:

• Create an X social listening profile report: Track recent visible posts from a public profile for brand or product monitoring.
• Archive a specific X status URL: Extract one or more exact public tweet URLs when the post ID matters.
• Export an X profile timeline without replies: Save top-level visible tweets from a profile and skip detected replies.

What you get

One saved visible tweet row with its ID, URL, author context, text and available public-page counts and media links. createdAt can be the source's displayed date label rather than a normalized exact timestamp. Null counts and missing visible posts are not zero engagement or proof of a complete empty timeline.

Who is it for?

• Editorial researchers collecting source-linked public post text for separate review.
• Brand and competitor analysts retaining bounded observations from known profiles.
• Creator research teams inspecting exposed content and media references.
• Data developers maintaining stable tweet IDs and source-page provenance in their own tools.

How you can use the data

• Review Apify's visible public posts. Use the existing Apify profile input and keep tweetId, tweetUrl, text and scrapedAt. The first public response need not include every recent post or an account's full history.
• Prepare a top-level brand-feed sample. Turn reply inclusion off for the existing profile and retain isReply. Reply detection reflects available page evidence rather than a full conversation export or a guarantee that every reply was identified.
• Archive a known status deliberately. Supply your known public status URL when a specific tweet ID matters, retaining the source URL and exposed content. The IDs in the illustrative examples show the expected format. They do not identify verified existing posts.
• Make your own repeated content comparison. Store IDs, public date labels and collection times before producing a topic report or monitoring alert. Counts can differ from logged-in or localized views, and downstream summaries or change detection are your own work.

Input settings

Setting	JSON key	Use it for	Example
Profile URLs	profileUrls	Public X/Twitter profiles to scan.	[{"url":"https://x.com/Apify"}]
Status URLs	statusUrls	Optional individual public tweet/status URLs to extract.	[{"url":"https://x.com/Apify/status/1234567890"}]
Maximum tweets per profile	maxTweetsPerProfile	Cap visible tweets saved from each profile URL.	10
Include replies	includeReplies	Keep or skip tweets detected as replies.	true
Connection	connectionMode	Automatic by default, or Direct. See field help for costs and saved-setting precedence.	"automatic"
Maximum run time	maxRuntimeSeconds	Optional 45–270 second work budget, with a five-minute maximum when omitted. Unfinished URLs are checkpointed.	45
Resume pending work	resumeState	Optional PENDING_WORK checkpoint from an interrupted run.	{"pendingUrls":["https://x.com/Apify"]}
Saved proxy settings	proxyConfiguration	Optional existing proxy settings that override Connection.	{"useApifyProxy":true}

Output data

This synthetic, shape-only row illustrates the output format. Its identifiers and values do not describe a verified post:

{
  "profileUrl": "https://x.com/Apify",
  "username": "Apify",
  "displayName": "Apify",
  "tweetId": "1234567890123456789",
  "tweetUrl": "https://x.com/Apify/status/1234567890123456789",
  "text": "Build web scrapers, automations, and data extraction workflows with Apify.",
  "createdAt": "Jul 3",
  "replyCount": 2,
  "repostCount": 6,
  "likeCount": 42,
  "viewCount": 1200,
  "mediaUrls": [],
  "isReply": false,
  "scrapedAt": "2026-07-03T10:00:00.000Z"
}

The actor returns one dataset row per saved public tweet.

Field	Description
profileUrl	Source profile URL when the tweet came from a profile page
username	X username
displayName	Display name when visible
tweetId	Tweet/status ID
tweetUrl	Public tweet URL
text	Tweet text extracted from the public page
createdAt	Visible date or time label from the page
replyCount	Reply count when visible
repostCount	Repost count when visible
likeCount	Like count when visible
viewCount	View count when visible
mediaUrls	Public media image URLs found in the tweet block
isReply	Whether the tweet appears to be a reply
scrapedAt	ISO timestamp for extraction

Download your results

Open your run's dataset, choose Export and select JSON, CSV or Excel. JSON keeps nested fields together. CSV and Excel are useful when you want to review the records in a spreadsheet.

See Apify's download and export guide for the available formats and field options.

Pricing

The start event applies when a run starts, including runs that return no tweets. The result event charges for saved public tweet rows. Use a small per-profile cap and a focused input list to control work.

See the live Pricing tab for current event rates and plan discounts. Platform usage can also apply.

Tips for best results

• Start with one profile: Test a public profile URL and a small maxTweetsPerProfile value.
• Use status URLs for exact posts: Add statusUrls when you need specific tweet IDs instead of recent visible profile posts.
• Expect visible-page limits: The actor extracts what is visible in public page HTML, not an authenticated full archive.
• Filter replies intentionally: Set includeReplies to false for brand-feed monitoring when replies are less useful.
• Review null metrics: Engagement counts can be null when X does not render them in the public page response.
• Resume an interrupted batch: Copy the PENDING_WORK record into resumeState to retry only unfinished public URLs.
• Bound a batch deliberately: Set maxRuntimeSeconds to 45–270 for a short, checkpointed run. Omitting it still limits processing to five minutes.

Limits and caveats

• The actor extracts public X/Twitter pages only.
• It does not log in, access private profiles, scrape protected tweets, or bypass account restrictions.
• X page markup, visibility, rate limits, and anti-bot behavior can change.
• Each page response is limited to 8 MiB after decompression. Larger responses are stopped and reported as request failures, not empty results; mixed batches retain other saved rows, while all-input request failure fails the run.
• Very old posts or infinite-scroll content may not be visible from the first public page response.
• Counts and date labels are public-page values and can differ from logged-in or localized views.
• Missing or login-gated pages return no rows with a reason in RUN_SUMMARY. A response with no usable tweets does not establish that an account is private, deleted or has no posts.
• Mixed batches keep saved rows and report isolated request failures. Systemic request failures, invalid settings and essential output or billing failures still fail the run.

Only visible public-page HTML is parsed, so infinite-scroll history, old posts and account-restricted views can be absent. Different profile or status sources can have different public context. Missing engagement values stay unavailable rather than being filled with guesses.

The explicit resumeState input can retry URLs copied from PENDING_WORK after an interrupted batch. Keep the intended collection settings and inspect completed rows before a later run, which has its normal start event and can charge newly saved results. Charged executions stop rather than repeat extraction after a restart. Start a new run with unfinished URLs when needed. This is not a built-in cross-run archive, content diff or recurring alert service.

This actor extracts publicly visible X/Twitter page data.

Use the data responsibly, follow X's terms, Apify's terms, and applicable privacy, platform, copyright, and anti-spam laws.

Do not use exported data for harassment, spam, credential collection, or attempts to access private content.

Automation and integrations

Save your settings for next time

Once you have an input that works for you, save it as an Apify task. This keeps your settings together so you can use them again without filling in the form from scratch.

Run on a schedule

Need fresh results regularly? You can schedule the Actor or a saved task to run at a time that suits you.

Each scheduled run collects the data again. If you want to compare results or highlight changes, add that step in your own workflow.

Send results to your other tools

Use n8n, Make or Zapier to connect this scraper to the rest of your workflow. For example, you could pass its results to an AI assistant or add records to a spreadsheet. Follow the Apify integration guides for your chosen tool.

For a custom connection, an Apify webhook can notify your app when a run finishes or fails. Your app can then fetch the results or handle the failure.

API usage

Want to collect this data from your own app or automation? The examples below send input to the scraper and show how to collect its results.

The Node.js and Python examples wait for the run to finish before reading its results. The cURL example starts the run and returns its details. Wait for that run to finish, then use its defaultDatasetId to fetch the results.

For setup instructions, see Apify's JavaScript client guide, Python client guide and Actor runs API reference.

cURL

curl -X POST 'https://api.apify.com/v2/acts/fetch_cat~x-profile-tweets-scraper/runs?token=YOUR_APIFY_TOKEN' \
  -H 'Content-Type: application/json' \
  -d '{"profileUrls":[{"url":"https://x.com/Apify"}],"maxTweetsPerProfile":10,"includeReplies":true}'

Node.js

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('fetch_cat/x-profile-tweets-scraper').call({
  profileUrls: [{ url: 'https://x.com/Apify' }],
  maxTweetsPerProfile: 10,
  includeReplies: true
});

const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

Python

from apify_client import ApifyClient
import os

client = ApifyClient(os.environ["APIFY_TOKEN"])
run = client.actor("fetch_cat/x-profile-tweets-scraper").call(run_input={
    "profileUrls": [{"url": "https://x.com/Apify"}],
    "maxTweetsPerProfile": 10,
    "includeReplies": True,
})
items = client.dataset(run["defaultDatasetId"]).list_items().items
print(items)

MCP and AI agents

You can ask your AI assistant to collect data with X Profile Tweets Scraper and help you work with the results. The scraper returns the data, and your assistant can then summarize it, compare records or prepare notes.

Connect your assistant through the Apify MCP server. MCP gives your assistant a way to find this scraper, run it and read the results. Follow the official setup and sign-in guide for your app.

Easier setup with an Apify plugin

If you use a supported coding assistant, the official Apify plugin can set up the connection for you. It connects your assistant to Apify and includes instructions for common tasks. Follow the guide for your particular app.

Use Apify AI in Console

Prefer to keep everything in Apify? Open Apify AI in Console and ask it to find Fetch Cat's X Profile Tweets Scraper. You can describe the data you want and ask questions about the results.

Apify AI is currently in beta. It asks for confirmation before starting an Actor, and normal run charges apply.

Choose your assistant

• Claude and Claude Code (Anthropic): Apify setup guide.
• ChatGPT and Codex (OpenAI): Apify setup guides.
• Grok Bot (xAI): Apify plugin guide.
• Gemini CLI (Google): MCP server setup guide. Use the server URL below with the HTTP configuration supported by Gemini CLI.

Connect just this scraper

To keep your setup focused on this scraper, add this server configuration to a compatible MCP client:

{
  "mcpServers": {
    "apify": {
      "url": "https://mcp.apify.com?tools=fetch_cat/x-profile-tweets-scraper"
    }
  }
}

Sign in to Apify when your client asks. If your client uses a Bearer token instead, follow its setup guide and keep the token in its secure configuration. Configuration formats vary by app, so use the linked guide if your client needs a different format.

Use Apify's general server

Already connected to the general Apify MCP server at https://mcp.apify.com? You can use it to find this scraper without adding another server. Ask your assistant to use X Profile Tweets Scraper by Fetch Cat, or give it the identifier fetch_cat/x-profile-tweets-scraper.

Your assistant can check the available settings and retrieve the results from the returned run. If the run is still working, it should follow that run rather than start it again. Both connection options use Apify's hosted service.

Example requests

• “Use Fetch Cat’s X Profile Tweets Scraper to collect up to 5 visible posts from https://x.com/Apify with replies included. Keep tweet URLs, public date labels and missing engagement values without claiming a full archive.”
• “Collect up to 5 visible posts from https://x.com/Apify with replies excluded. Keep source identifiers and text for my own brand-feed review without generating missing posts or treating reply detection as a complete conversation.”
• “Retrieve up to 3 visible posts from https://x.com/Apify, preserving media URLs and available public counts. Keep observation times for my own later comparison without scheduling another run or inferring zero for missing metrics.”

Normal Apify charges apply. Check the live Pricing tab before asking your assistant to run a larger batch.

Pay with x402

If your AI agent has a funded wallet, it can pay for Apify usage through x402. This experimental option lets an agent use Apify without a conventional account.

Apify AGI provides a prepaid API token with a spending cap after payment. Your agent can use that token to run this scraper through the Apify API or an authenticated MCP connection.

Some MCP setups also support paying for each request directly. That is a different payment option, so check the official guide for its availability.

Follow the official guide for wallet setup, supported payment options and current terms. Apify handles the payments. Keep wallet keys and payment tokens in your agent's secure configuration.

Other ways for agents to pay

Apify also supports MPP for prepaid access through AGI and Skyfire for eligible Actors. If your agent already uses one of these, see the agentic payment guide to choose the right setup.

FAQ

Is this a complete timeline or historical archive?

No. It extracts the posts visible in public page responses. Older or infinite-scroll content can be missing.

Does a missing count mean zero engagement?

No. Counts can be absent when X does not render them, and public values can differ across views.

Can I exclude replies?

Yes. Set includeReplies false to skip detected replies, keeping the public-page detection limit in mind.

Can I use private accounts or log in?

No. The Actor does not log in, access protected tweets or bypass account restrictions.

Related Actors

Explore related actors from the same Apify account:

• TikTok Profile Scraper — Collect available public TikTok profile details and video metadata.
• Reddit Scraper — Collect public Reddit posts and optional comments from supported feeds, searches or discussion URLs.
• Telegram Channel Posts Scraper — Collect public Telegram channel posts and available engagement or media references.
• Bluesky Profile Feed Scraper — Collect public Bluesky profile details and recent author-feed posts from handles or DIDs.
• YouTube Comments Scraper — Collect available public YouTube video comments and exposed replies.

Support and feedback

For custom additions or integrations, email hello@fetchcat.dev.

Found an error or have a feature request? Open an issue with the run URL, a non-sensitive input example and what you expected.

Need help sharing it? See Apify’s guide to sharing a run when reporting an issue. Sharing a run can give the developer access to its input, logs and results, so use a run that contains no sensitive data. Please leave out API tokens, passwords, cookies, private documents and personal data. Use a public sample URL or a redacted example instead.

Tried this scraper? We'd love to hear how it worked for you. Leave a review to help others choose the right tool and help us improve it. Your feedback means a lot to us.

Made with care for curious people, AI agents and the possibilities in data. ♥