X Profile Metrics Scraper avatar

X Profile Metrics Scraper

Pricing

from $0.75 / 1,000 x profile metric snapshots

Go to Apify Store
X Profile Metrics Scraper

X Profile Metrics Scraper

Extract public X profile identity, bio, verification, links, and follower, following, post, media, like, and list counts from handles or URLs.

Pricing

from $0.75 / 1,000 x profile metric snapshots

Rating

0.0

(0)

Developer

Chronometrica

Chronometrica

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

3 days ago

Last modified

Share

๐Ÿ“Š What does X Profile Metrics Scraper do?

X Profile Metrics Scraper turns public X or Twitter profile URLs and handles into clean profile snapshots. Use it for creator checks, lead lists, account tracking, reports, and scheduled data updates.

Each input creates one stable row with profile identity, bio, links, account flags, and public counts.

This Actor reads public logged-out X data. It does not use cookies, log in to X, collect follower lists, or open private account data.

With X Profile Metrics Scraper, you can:

  • ๐Ÿ“ˆ Track follower, following, and post counts.
  • ๐Ÿง‘โ€๐Ÿ’ป Build clean creator or company profile lists.
  • โœ… Check verification and account flags.
  • ๐Ÿ”— Collect public bios, websites, and profile links.
  • ๐Ÿ“ฆ Export rows to JSON, CSV, Excel, XML, RSS, or an API.

๐Ÿ“ฆ What X profile data can I extract?

One dataset row represents one attempted public X profile input.

Data groupExample fields
๐Ÿ”— Profile identityinput, profileId, profileUrl, handle, displayName
๐Ÿงพ Public detailsbiography, website, location, joinedAt
๐Ÿ–ผ๏ธ ImagesavatarUrl, bannerUrl
โœ… Account flagsisBlueVerified
๐Ÿ“Š Public metricsfollowers, following, posts, media, liked posts, and lists
๐ŸŽฏ QualityprofileMetricStatus, status, statusReason
๐Ÿ•’ ObservationobservedAt

Missing public values stay null. They are never changed to a made-up zero. profileMetricStatus shows which counts were exact and which were unavailable.

โš™๏ธ Can I use X Profile Metrics Scraper through an API?

Yes. Run it in Apify Console or connect it through:

  • Apify API
  • Python SDK
  • JavaScript SDK
  • Webhooks
  • Scheduled Tasks
  • Apify integrations

๐ŸŽฏ Why collect X profile metrics?

Use caseHow the data helps
๐Ÿง‘โ€๐ŸŽจ Creator researchCompare public audience size and account details.
๐Ÿงฒ Lead listsAdd stable profile IDs, handles, bios, and websites.
๐Ÿ“ˆ Account trackingSave repeated public profile snapshots over time.
๐Ÿงฑ Data pipelinesLoad clean profile rows into a sheet or warehouse.

๐Ÿ’ต Pricing event

The product is designed for pay-per-result pricing. One paid result means one successfully resolved public profile row. Failed rows are free.

The price ranges from $0.75 to $1.50 per 1,000 results, based on your Apify plan. Platform usage is included. Use Apify's maximum charge setting to cap paid results.

๐Ÿš€ How do I use X Profile Metrics Scraper?

  1. Open X Profile Metrics Scraper in Apify Console.
  2. Add one or more X profile URLs, handles, or user names.
  3. Click Start.
  4. Open the Output tab.
  5. Download the dataset or connect it to your workflow.

โฌ‡๏ธ Input

Add up to 1,000 public X profile URLs or handles, with or without @, to profiles.

{
"profiles": ["https://x.com/OpenAI", "@NASA", "github"]
}

Duplicate inputs are checked once. Search pages, post URLs, lists, follower lists, and following lists are not supported.

โฌ†๏ธ Output sample

{
"platform": "x",
"input": "https://x.com/OpenAI",
"profileId": "4398626122",
"profileUrl": "https://x.com/OpenAI",
"handle": "@OpenAI",
"displayName": "OpenAI",
"biography": "",
"website": "https://openai.com",
"location": null,
"followersCount": 5000000,
"followingCount": 4,
"postsCount": 9000,
"profileMetricStatus": {
"followersCount": "exact",
"followingCount": "exact",
"postsCount": "exact",
"mediaCount": "unavailable",
"likedPostsCount": "unavailable",
"listedCount": "exact"
},
"status": "ok",
"failureCategory": null,
"statusReason": null,
"observedAt": "2026-07-17T12:00:00.000Z"
}

Good and failed rows use the same ordered fields. Failed rows keep unknown values as null. failureCategory separates safe causes such as a network failure or empty response without exposing raw source data.

๐Ÿ“Œ Run summary

The OUTPUT record reports input count, unique inputs, saved rows, billable rows, status counts, start time, finish time, and runtime.

๐Ÿšฆ Status and quality fields

failureCategory is null for good rows. Failed rows use a safe category such as network, empty_response, rate_limit, access, or unknown.

  • ok: the public profile identity was proven.
  • not_found: the profile does not exist or is no longer available.
  • private: the account does not show public profile data.
  • blocked: X challenged the public request.
  • rate_limited: X asked the run to slow down.
  • login_required: X required a signed-in view at that time.
  • parser_miss: X returned data without a stable profile identity.
  • invalid_input: the value was not a profile URL or handle.
  • failed: another safe source error happened.

๐Ÿ”’ Source boundary

This Actor reads only data X shows without signing in. It does not use your X account, cookies, passwords, or private tokens. It does not bypass login or challenge screens.

โš ๏ธ Limits

  • Full follower and following lists are not included.
  • Deleted, blocked, region-limited, or private accounts may fail.
  • X may hide some fields. Hidden values stay null.
  • Results are snapshots. Use a schedule to build history.
  • X can change its public pages, so a later run may need an Actor update.

โ“ FAQ

Does this Actor need an X login or API key?

No. It reads logged-out public X data.

Why is a profile count null?

X did not show that value publicly for the profile at run time. Check profileMetricStatus and the row status.

How are duplicate profiles handled?

The same normalized handle is checked once per run.

ActorUse it for
X Post Metrics ScraperTrack public views, likes, replies, reposts, quotes, and bookmarks for known X post URLs.

๐Ÿ›Ÿ Support

For help, share the public profile URL, run ID, expected result, and actual result. Never share passwords, cookies, or private tokens.

Use public data in line with the law, X rules, and Apify rules.