User Scraper

Discover X users and understand accounts beyond tweets with profile data, followers, or following data for research, outreach, and audience analysis.

New: search for X users

You can now discover X accounts even when you do not know their exact handles. Select the search input type and enter a name, handle fragment, brand, role, or keyword in searchQuery. The Actor returns matching user profiles with fields such as username, display name, bio, profile URL, verification status, and audience counts.

This makes the User Scraper useful for:

• finding a person from a partial name, such as elon
• discovering creators, experts, founders, or brands in a niche
• building prospect and influencer lists from keywords
• finding the correct account before collecting its followers or following

Search mode supports pagination through page and maxPages, page size through limit, and a total result cap through maxItems.

About SIMO IT

SIMO IT provides actionable scraping solutions that convert social graph data into growth and research signals.

Features

• collect profile data for one or many X handles
• search X users by name, handle, or keyword
• fetch only followers as a flat dataset
• fetch only following as a flat dataset
• analyze network overlap and relationship patterns
• build lead lists and influencer maps

Use cases

• account research before outreach and partnerships
• audience and community analysis
• profile segmentation for sales and marketing campaigns

Output

Choose one output mode per run: exact user profiles, user search results, followers, or following.

How to use

1. Open the Actor on Apify.
2. Provide handles/userUrls, or enter searchQuery in search mode.
3. Choose whether you want users, search, followers, or following.
4. Configure pagination and run the Actor.

No technical setup is required from your side. Backend infrastructure is managed by SIMO IT.

Pricing note: profile lookup pricing was updated because fetching a single profile still requires a full backend/X request, even though it usually returns only one dataset row. The previous row-based price underpriced profile-only runs and could fall below the real infrastructure and runtime cost. Profile lookups, follower pages, and following pages are now tracked separately so pricing can better reflect the actual work performed.

Need a custom plan, custom limits, or a tailored data workflow? Contact contact@simoit.tech.

Related Actors

• Need tweet content instead of account metadata? Use Tweet Scraper.
• Need posts from one selected profile? Use Profile Scraper.
• Need list-based monitoring across curated sources? Use List Scraper.
• Need trend discovery before mapping who matters in a topic? Use Trends Scraper or Global Trending Scraper.

Input

• inputTargetType (string, optional, default: users): Output mode.
  • users: return profile records
  • search: search X accounts and return matching profile records
  • followers: return follower records for each source handle
  • following: return following records for each source handle
• handles (string, conditionally required): X usernames (without @), comma-separated or new lines.
• userUrls (string, optional): X/Twitter profile URLs (comma-separated or new lines).
• searchQuery (string, conditionally required): Search text used when inputTargetType is search.
• page (integer, optional, default: 1): Starting page number.
• limit (integer, optional, default: 20, max: 100): Records per page.
• maxPages (integer, optional, default: 1): Number of pages to fetch starting from page. Example: page=2 and maxPages=3 fetches pages 2..4.
• maxItems (integer, optional): Maximum profile records in search mode.
• followersMaxItems (integer, optional): Maximum followers per handle.
• followingMaxItems (integer, optional): Maximum following per handle.

Filters and pagination

• user target: handles, userUrls, or searchQuery
• output mode: inputTargetType
• page controls (search/followers/following): page, limit, maxPages
• output caps: maxItems, followersMaxItems, followingMaxItems

Example input

{
  "inputTargetType": "followers",
  "userUrls": "https://x.com/openai, https://twitter.com/apify",
  "limit": 20,
  "followersMaxItems": 100
}

Search users example

{
  "inputTargetType": "search",
  "searchQuery": "elon",
  "limit": 20,
  "maxPages": 1,
  "maxItems": 20
}

The example above returns matching accounts such as elonmusk. Search results use the same user profile structure as exact profile lookups:

{
  "search_query": "elon",
  "handle": "elonmusk",
  "user": {
    "id_str": "44196397",
    "username": "elonmusk",
    "displayname": "Elon Musk",
    "url": "https://x.com/elonmusk"
  }
}

Example output

{
  "source_handle": "openai",
  "source_user_id": 4398626122,
  "relationship": "follower",
  "user": {
    "id": 12345,
    "username": "example_follower",
    "displayname": "Example Follower"
  }
}

FAQ

Do I need my own backend or API setup?
No. This Actor is ready to run on Apify, and backend infrastructure is managed by SIMO IT.

Can I run multiple handles in one job?
Yes. Pass multiple usernames in handles as comma-separated or newline-separated text.

What is the difference between users and search?

Use users when you already know the exact handles or profile URLs. Use search when you want to discover matching accounts from a name, partial handle, brand, or keyword.

Will this return followers and following by default?
No. The default mode is users. Switch inputTargetType to followers or following.