X Profile & Post Monitor - Twitter Account Changes

Monitor public X/Twitter accounts for new posts and meaningful profile changes without login credentials or an API key. Collect current profile snapshots, recent posts, engagement metrics, media links, and change events in one clean dataset.

What this Actor does

• Extracts public X profile names, bios, locations, websites, avatars, and banners
• Tracks followers, following, post counts, and verification status
• Collects recent visible posts with likes, reposts, replies, bookmarks, views, and media
• Emits only new posts on recurring monitoring runs
• Detects profile changes such as a new bio, display name, website, avatar, or banner
• Filters posts by age, keywords, replies, and reposts
• Runs over HTTP with no browser, X login, or API key

Quick start

{
  "handles": ["OpenAI", "Apify", "vercel"],
  "maxPostsPerProfile": 10,
  "publishedWithinDays": 30
}

Monitor only changes and new posts

Enable monitorChangesOnly and choose a stable stateKey. The first run returns the current profile and visible posts. Later runs return only new posts and profile-change records.

{
  "handles": ["OpenAI", "AnthropicAI", "GoogleDeepMind"],
  "monitorChangesOnly": true,
  "stateKey": "ai-company-x-monitor",
  "maxPostsPerProfile": 20,
  "includeReplies": false,
  "includeReposts": false
}

Use a different state key for each independent scheduled monitor. Connect an Apify webhook to Slack, email, Make, Zapier, Google Sheets, or your own API to receive changes automatically.

Filter posts by topic

{
  "handles": ["OpenAI", "GoogleDeepMind", "MicrosoftAI"],
  "includeKeywords": ["model", "API", "launch", "research"],
  "excludeKeywords": ["hiring"],
  "publishedWithinDays": 14
}

Output record types

• profile — current public profile snapshot
• profileChange — current snapshot plus changedFields and previous values
• post — recent or newly detected public post with engagement and media fields

Input fields

Field	Description
handles	X handles or profile URLs.
handlesText	Bulk profile list, one per line.
maxPostsPerProfile	Recent visible posts kept per profile.
publishedWithinDays	Maximum post age; 0 disables filtering.
includeReplies	Include visible replies.
includeReposts	Include visible reposts.
includeKeywords	Keep posts matching at least one term.
excludeKeywords	Remove posts matching any term.
monitorChangesOnly	On later runs, output only new posts and profile changes.
stateKey	Stable identifier for persistent monitor state.
maxProfiles	Safety limit, up to 1,000 profiles.
proxyConfiguration	Optional proxy settings for larger repeated runs.

Suggested uses

• Competitor and executive account monitoring
• Brand and communications alerts
• Influencer watchlists
• Journalist and newsroom source tracking
• Product-launch monitoring
• Public profile compliance and change history
• Social content pipelines

Limits

X controls which public timeline posts appear in its logged-out profile pages, so this Actor returns the recent posts visible there rather than a complete historical archive. Private, suspended, age-restricted, and login-only accounts are not supported. X may change its public page format; extraction errors are reported per profile without discarding successful profiles.

Use public data responsibly and follow X's terms and applicable privacy laws.

API example

curl -X POST \
  "https://api.apify.com/v2/acts/groupoject~x-profile-post-monitor/run-sync-get-dataset-items?token=YOUR_APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"handles":["OpenAI","Apify"],"maxPostsPerProfile":10,"publishedWithinDays":30}'

Example post output

{
  "recordType": "post",
  "handle": "OpenAI",
  "text": "Public post text",
  "postUrl": "https://x.com/OpenAI/status/123",
  "likes": 1250,
  "reposts": 210,
  "replies": 84,
  "views": 120000,
  "mediaUrls": [],
  "publishedAt": "2026-09-01T12:00:00.000Z"
}

Monitoring tips

• Establish the baseline before enabling workflows that expect changes only.
• Reuse the exact same stateKey for every run in one monitor.
• Use separate state keys for competitors, executives, journalists, or campaigns.
• Keep concurrency low for frequent monitoring.
• Apply inclusion keywords to reduce noisy alert feeds.

FAQ

Is an X API key or account required?

No. The Actor uses public logged-out X surfaces and does not require developer API credentials.

Does it provide a complete post archive?

No. It returns the recent posts X exposes publicly. It is designed for snapshots and monitoring, not historical archive recovery.

What profile changes are detected?

Depending on available public data, changes can include display name, bio, website, avatar, banner, location, verification, and public counts.

Can it monitor private accounts?

No. Private, suspended, restricted, or login-only profiles are outside its supported scope.

Pricing and billing

Base result price checked September 14, 2026: $2.00 per 1,000 dataset items ($0.002 each). 100 result items cost $0.20 in result fees.

The separate Actor start event is $0.0005 per billable start unit, with one unit per GB of configured memory and a minimum of one. It applies even when a run returns no results.

A result event corresponds to one item saved in the default dataset, not one HTTP request or one input URL.

The live Pricing tab is authoritative for current rates, tier discounts and any separately charged usage. Set a maximum run charge and inspect a small sample before scaling. Charges from an external provider, where used, are not controlled by the Apify run-charge limit.