X Twitter Profiles, Posts, Replies & Monitoring

Collect public X profiles, posts, replies, search results, engagement metrics, and monitoring deltas in structured datasets.

All examples below use fictional DEMO-* identifiers, reserved .test domains, and masked contact details. They do not represent real people, listings, products, or companies.

🚀 What this Actor does

• Flexible collection: PROFILES, USER_POSTS, PROFILE_SEARCH, POST_DETAILS, MONITOR.
• Structured output: clean JSON records organized into results, profiles, posts, replies, changes views.
• Production-ready: concurrency, retries, proxy support, limits, and source-aware diagnostics are exposed through the Actor input.
• Easy automation: run from the Apify Console, API, schedules, webhooks, Make, Zapier, or any HTTP client.

🎛️ Modes and workflows

Mode or workflow	What it does
PROFILES	Collect public profile identity and audience metrics.
USER_POSTS	Collect recent public posts from selected profiles.
PROFILE_SEARCH	Search public posts and profiles by query and filters.
POST_DETAILS	Resolve exact post URLs and optional public replies.
MONITOR	Track new posts and engagement deltas with a named monitor.

💡 Common use cases

• Public profile and content research
• Topic and engagement monitoring
• Post, reply, and media datasets

📥 Input schema

Configure the Actor in the Input tab or send the same JSON through the API. Fields not needed for your workflow can be omitted.

Field	Type	Description	Default
scrapeType required	string	Choose the public X data you want in the dataset. Allowed: PROFILES, USER_POSTS, PROFILE_SEARCH, POST_DETAILS, MONITOR.	PROFILES
usernames	array<string>	Used by Profiles, Recent posts, Search, and Monitor. Enter NASA, @NASA, or https://x.com/NASA.	—
maxPostsPerProfile	integer	Used by Recent posts, Search, and Monitor. Increase this to inspect a deeper part of each public timeline.	20
includeReposts	boolean	Keep reposts shown in profile timelines. Original posts are always included.	false
postUrls	array<string>	Used only by Posts by URL. Both x.com and twitter.com links are accepted.	—
includeReplies	boolean	Save replies that X exposes publicly for each requested post.	true
maxReplies	integer	Maximum public replies to save for one post. Availability depends on what X exposes publicly.	20
queries	array<string>	Used only by Search inside profiles. Supports phrases, excluded words, from:, lang:, min_faves:, min_retweets:, min_replies:, and filter: operators.	—
startDate	string	Optional inclusive date in YYYY-MM-DD format, for example 2026-08-01.	``
endDate	string	Optional inclusive date in YYYY-MM-DD format.	``
includeKeywords	array<string>	Keep a post when its text contains at least one value. Matching is case-insensitive.	—
excludeKeywords	array<string>	Remove a post when its text contains any value. Matching is case-insensitive.	—
language	string	Optional 2–3 letter language code such as en, ru, es, de, or ja.	``
mediaFilter	string	Keep every post or select a specific kind of media. Allowed: ANY, WITH_MEDIA, IMAGES, VIDEOS, WITHOUT_MEDIA.	ANY
verifiedOnly	boolean	Keep posts only when X marks the author as verified.	false
minLikes	integer	Keep posts with at least this many likes.	0
minReposts	integer	Keep posts with at least this many reposts.	0
minReplies	integer	Keep posts with at least this many replies.	0
minViews	integer	Keep posts with at least this many public views.	0
monitorKey	string	Optional stable name such as nasa-launch-watch. Reuse it on every scheduled run.	``
emitInitialPosts	boolean	First run: save current posts as BASELINE. Later runs save only NEW or UPDATED posts.	true
maxResults	integer	Hard cap for dataset rows. Combine it with Apify's Maximum charge per run for strict cost control.	100
maxConcurrency	integer	Targets processed in parallel. The default is fast and stable for most runs.	10
maxRetries	integer	Attempts allowed after a temporary network or X response problem.	3
timeoutSecs	integer	Maximum time allowed for one public X request.	20
proxyConfiguration	object	Optional proxy configuration. Direct requests are used by default.	{"useApifyProxy": false, "proxyUrls": []}

▶️ Example input

{
  "scrapeType": "PROFILE_SEARCH",
  "queries": [
    "product launch"
  ],
  "language": "en",
  "mediaFilter": "WITH_MEDIA",
  "maxResults": 50
}

📦 Output schema

Each successful item is written to the default dataset. Select a dataset view in the Apify Console or export the full dataset as JSON, CSV, Excel, XML, or RSS.

results — All results

Unified primary results across the selected workflow.

Fields: imageUrl, profileImageUrl, recordType, sourceUsername, searchQuery, username, displayName, changeType, text, followersCount, likeCount, repostCount, replyCount, viewCount, engagementRate, language, mediaType, publishedAt, url, scrapedAt

profiles — Profiles

Profile-level identity and audience records.

Fields: profileImageUrl, sourceUsername, username, displayName, bio, bioEmails, location, website, followersCount, followingCount, followerFollowingRatio, postsCount, postsPerDay, accountAgeDays, averagePostLikes, averagePostViews, isVerified, isBlueVerified, verifiedType, createdAt, url, scrapedAt

posts — Posts

Post-level content and engagement records.

Fields: imageUrl, sourceUsername, searchQuery, username, displayName, postType, isRepost, repostedByUsername, text, publishedAt, likeCount, repostCount, replyCount, quoteCount, bookmarkCount, viewCount, totalEngagement, engagementRate, language, mediaType, hashtags, mentions, links, mediaUrls, videoUrls, quotedUsername, quotedText, url, scrapedAt

replies — Replies

Reply-level public conversation records.

Fields: profileImageUrl, sourceUsername, username, displayName, text, publishedAt, likeCount, repostCount, replyCount, quoteCount, viewCount, totalEngagement, engagementRate, language, mediaType, conversationId, sourcePostId, url, scrapedAt

changes — Monitoring changes

Monitoring events and field-level deltas.

Fields: imageUrl, sourceUsername, username, changeType, changedFields, text, publishedAt, likeCount, likeDelta, repostCount, repostDelta, replyCount, replyDelta, viewCount, viewDelta, monitorKey, detectedAt, url

📤 Example output

{
  "sourceUsername": "demo_account",
  "searchQuery": "product launch",
  "username": "demo_account",
  "displayName": "Demo Account",
  "postType": "post",
  "text": "Example public post used only for documentation.",
  "publishedAt": "2026-08-15T12:00:00Z",
  "likeCount": 420,
  "repostCount": 38,
  "replyCount": 19,
  "viewCount": 18400,
  "language": "en",
  "mediaType": "image",
  "url": "https://x.com/demo_account/status/DEMO-POST-01"
}

Missing source values are returned as null, empty arrays, or documented availability/status fields; the Actor does not invent unavailable source data.

🔌 API example

Replace the placeholder with an Apify token and send the same input used in the Console:

curl -X POST "https://api.apify.com/v2/acts/trakk~x-twitter-public-data-scraper/runs?token=<YOUR_APIFY_TOKEN>" \
  -H "Content-Type: application/json" \
  -d '{"scrapeType": "PROFILE_SEARCH", "queries": ["product launch"], "language": "en", "mediaFilter": "WITH_MEDIA", "maxResults": 50}'

For synchronous integrations, use the run-sync-get-dataset-items API endpoint. For larger jobs, start an asynchronous run and consume its default dataset when the run succeeds.

🧩 Automation and exports

• Schedule recurring runs from the Apify Console.
• Trigger downstream systems with webhooks when a run succeeds or fails.
• Reuse named monitoring keys or stores where the selected workflow supports change tracking.
• Export dataset views to JSON, CSV, Excel, XML, or RSS, or access items through the Apify API.

❓ FAQ

Do I need a login or browser session?

Use only the inputs shown in the Actor schema. If authentication or cookies are supported, the relevant encrypted field is explicitly available in the Input tab; otherwise no account is required.

Why can some fields be empty?

Source pages vary by region, content type, privacy settings, and availability. Optional enrichment also depends on the selected mode. Empty values are preserved honestly instead of being guessed.

How should I run this at scale?

Start with a small representative input, inspect the dataset and cost, then raise item limits and concurrency gradually. Use Apify Proxy when the schema exposes it, and use schedules plus monitoring keys for recurring collection.

Is the example data real?

No. Every example in this README is intentionally fictional and uses demo identifiers, reserved domains, or masked contact values.