Twitter User Scraper – Export public X profiles

This Twitter user scraper exports enrichment-ready public X user profile data by handle, profile URL, or search query. Use the Twitter profile scraper dataset for creator discovery, social listening, public-source research, lead enrichment, and recurring profile monitoring. Run it as an X profile data API without providing an X login.

What you can export

• Canonical profile identity, URLs, name, biography, location, and public website
• Follower, following, and post counts when displayed publicly
• Avatar, banner, account creation date, verification, and protection status
• Request provenance, collection timestamp, and explicit warnings
• Conservatively extracted public email addresses and website domains

Example input

{
  "handles": ["NASA", "SpaceX"],
  "profileUrls": ["https://x.com/github"],
  "searchQueries": ["space agency"],
  "maxItems": 20,
  "includeRecentCounts": true,
  "failOnBlocked": false
}

Example output

{
  "id": "11348282",
  "handle": "NASA",
  "displayName": "NASA",
  "bio": "Making the seemingly impossible, possible. ✨",
  "location": "Pale Blue Dot",
  "websiteUrl": "http://www.nasa.gov/",
  "profileUrl": "https://x.com/NASA",
  "followersCount": 92338258,
  "postsCount": 74170,
  "isBlueVerified": true,
  "verifiedType": "Government",
  "sourceType": "handle",
  "scrapedAt": "2026-08-20T22:27:52.191Z",
  "websiteDomains": ["nasa.gov"],
  "status": "ok"
}

Input settings

Field	Type	Default	Description
handles	string[]	[]	Public handles, with or without @
profileUrls	string[]	[]	Public x.com or twitter.com profile URLs
searchQueries	string[]	[]	Find public profiles relevant to each query
maxItems	integer	20	Global profile limit, from 1 to 1,000
includeRecentCounts	boolean	true	Include the visible postsCount; false emits null for that field
failOnBlocked	boolean	false	Fail rather than preserve partial results if a route is blocked

At least one handle, URL, or query must resolve to a public profile. Duplicate handles and URL aliases are merged.

Output fields

Fields	Meaning
id, handle, displayName	Stable public profile identity
bio, location, websiteUrl	Profile-supplied public details
profileUrl, legacyProfileUrl	Canonical X and compatible Twitter URLs
avatarUrl, bannerUrl	Public profile images
followersCount, followingCount, postsCount	Visible profile counters
likesCount, listedCount, mediaCount	Additional public counters when the source exposes them
createdAt	Account creation timestamp
isVerified, isBlueVerified, verifiedType	Public verification state
isProtected, canDm	Public privacy and messaging flags when exposed
professionalType, professionalCategories	Public professional-profile metadata
pinnedPostIds, withheldInCountries	Public pin and restriction metadata when exposed
sourceInput, sourceType, searchQuery	Input provenance
scrapedAt, status, warnings	Collection and diagnostic information
emails, websiteDomains	Conservative enrichment derived from public bio/link text

Optional source fields are null or empty when the profile does not publish them. The Actor never substitutes viewer locale or proxy geography for account data.

Input recipes

Monitor known accounts: provide a scheduled list in handles and export the latest public counters. Set includeRecentCounts: false when a stable identity-only snapshot is preferred.

Normalize profile URLs: mix x.com and twitter.com URLs; output uses stable canonical URLs.

Discover profiles: add focused terms to searchQueries, then bound the dataset with maxItems.

Who is it for?

This Actor is designed for social-listening teams monitoring public accounts, creator marketers building outreach lists, OSINT researchers comparing public profile changes, and sales intelligence teams enriching CRM records with public X identity and audience data.

Pricing

The Actor uses pay per event: one small run-start charge and one Profile exported event for each successfully saved row. Failed or blocked profiles are not charged as results. See the live Pricing tab for current tier rates.

API usage

cURL

curl -X POST "https://api.apify.com/v2/acts/fetch_cat~x-user-profile-scraper/runs?token=$APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"handles":["NASA"],"maxItems":1}'

JavaScript

import { ApifyClient } from 'apify-client';
const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('fetch_cat/x-user-profile-scraper').call({ handles: ['NASA'], maxItems: 1 });
const { items } = await client.dataset(run.defaultDatasetId).listItems();

Python

from apify_client import ApifyClient
import os
client = ApifyClient(os.environ['APIFY_TOKEN'])
run = client.actor('fetch_cat/x-user-profile-scraper').call(run_input={'handles': ['NASA'], 'maxItems': 1})
items = client.dataset(run['defaultDatasetId']).list_items().items

MCP and AI agents

Connect through Apify MCP to let an AI workflow run profile lookups and consume structured results.

$claude mcp add apify --transport http https://mcp.apify.com/?tools=fetch_cat/x-user-profile-scraper

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

Example prompts: “Export NASA and SpaceX public X profile counters” or “Find public X profiles for space agencies and return their websites.” Keep limits low while developing an automation.

Tips and limits

• Prefer exact handles or profile URLs when identity accuracy matters.
• Search results depend on public indexing and may not include every X account.
• Counts change continuously and represent the value visible at collection time.
• Removed, suspended, age-gated, or unavailable profiles may produce no row.
• Public-source availability and X anti-automation responses can cause partial runs; inspect run logs and warnings.
• The Actor exports public profile metadata only. It does not access DMs, private content, authenticated timelines, tweets, or follower graphs.

FAQ

What data can I export with twitter user scraper?

You can export public profile identity, bio, links, images, audience and post counts, verification state, timestamps, provenance, and conservative public contact enrichment.

Can I run X User Profile Scraper through an API, schedule, or MCP client?

Yes. Call it through the Apify API or SDK, connect it to an MCP client, or save the input as an Apify Task and schedule recurring exports.

Does this require my X password or API token?

No. The Actor works with publicly available profile information and never asks for X credentials.

Can I scrape private profiles or direct messages?

No. Those are outside this Actor's public-profile scope.

Why is an optional field null?

The profile or currently available public page did not expose it. Nulls are preferred over guessed values.

Can I schedule recurring exports?

Yes. Save the input as an Apify Task and schedule it from the Apify Console.

Related Actors

• X Profile Tweets Scraper for public posts by profile
• X Followers Scraper for follower workflows
• GitHub Profile Scraper for developer enrichment
• LinkedIn Profile Details Scraper for professional profiles
• TikTok Profile Scraper for creator profile data

Support

For questions or reproducible problems, open an issue from the Actor's Issues tab. Include the public input, run ID, and expected behavior; never include passwords or private account data.