# Threads Profile Scraper - Followers, Bio & Emails, No Login (`alom/threads-profile-scraper`) Actor

Get Threads profile data without logging in: follower count, full name, bio, bio links, e-mails and phones listed in the bio, verification and profile picture, plus the latest posts if you want them. Usernames or profile URLs. From $1.50 per 1,000 results.

- **URL**: https://apify.com/alom/threads-profile-scraper.md
- **Developed by:** [Alom Dev](https://apify.com/alom) (community)
- **Categories:** Social media, Lead generation, Agents
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.50 / 1,000 results

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## Threads Profile Scraper: Followers, Bio, Links & Emails, No Login

Get **Threads profile data** for a list of accounts: one row per account with the follower count, full name, bio,
bio links, the e-mails and phone numbers people put in their bio, verification, profile picture and topic tags.
Optionally add each account's **latest posts** with likes, replies, reposts and views.

- **No login needed.** It reads what a logged-out visitor of threads.com sees. No account of yours is involved.
- **Fast and cheap:** one request per profile. 8 profiles took 15 seconds in our test.
- **Contacts for outreach:** `emails`, `phones` and `bioLinks` come out of the bio as separate fields.
- **Usernames, @handles or profile URLs** (threads.com or threads.net), in any mix.
- **Latest posts on request,** with filters for likes, language and date, and engagement rate per post.
- Export to CSV, Excel or JSON, or pull results through the Apify API, Make, Zapier or n8n.

This Actor is a focused version of the [Threads Scraper](https://apify.com/alom/threads-scraper) (same code, same
prices). To find accounts by keyword instead of by name, use the
[Threads Account Finder](https://apify.com/alom/threads-lead-finder).

### What can you use it for?

- **Influencer vetting:** followers, verification, bio and real engagement per post before you reach out.
- **Lead lists:** enrich a list of Threads handles with the contact e-mails and links they publish.
- **Competitor tracking:** follower counts over time on a schedule.
- **CRM enrichment:** add Threads followers and bio to the accounts you already have.

### Input

| Field | What it does |
|---|---|
| `usernames` | Usernames, `@handles` or profile URLs, e.g. `zuck`, `@mosseri`, `https://www.threads.com/@nasa`. |
| `includePosts` | Also return each account's latest posts. Default off (profile rows only). |
| `maxPosts` | Max posts per account when `includePosts` is on. Default 20. |
| `postedAfter` | Only posts after a date, e.g. `2026-10-01` or `30 days`. Paging stops at older posts. |
| `minLikes` | Keep only posts with at least this many likes. |
| `languages` | Keep only posts in these languages, e.g. `["en"]`. |
| `includeViews` | Fill `viewCount` on every post. One extra request per post, about 1.5 s each, not charged. |

```json
{ "usernames": ["zuck", "@mosseri", "https://www.threads.com/@nasa"] }
```

```json
{ "usernames": ["mosseri"], "includePosts": true, "maxPosts": 30, "includeViews": true }
```

Other scrapers' field names work too: `profiles`, `urls` and `startUrls` are read as usernames or profile URLs.

### Output example

```json
{
    "type": "profile",
    "username": "nasa",
    "fullName": "NASA",
    "userId": "28829152388",
    "biography": "Making the seemingly impossible, possible. ✨",
    "followerCount": 12780727,
    "isVerified": true,
    "isPrivate": false,
    "profilePicUrl": "https://scontent…jpg",
    "bioLinks": [],
    "emails": [],
    "phones": [],
    "profileTags": ["NASA", "Space Threads", "Science Threads"],
    "followingCount": null,
    "url": "https://www.threads.com/@nasa",
    "source": "user:nasa",
    "scrapedAt": "2026-10-16T10:48:36.900Z"
}
```

`profilePicUrl` is the largest version Threads has. `emails` and `phones` are what the person wrote in the bio, so
most accounts have none. `followingCount` is `null` because Threads doesn't show it to logged-out visitors. With
`includePosts`, post rows (`type: "post"`) follow each profile row, with `likeCount`, `replyCount`, `repostCount`,
`viewCount`, `engagementRate`, `media`, `language` and `date`; see the
[Threads Scraper](https://apify.com/alom/threads-scraper) for every field.

### How much does it cost?

The same prices as the Threads Scraper: **from $1.50 per 1,000 results**, plus $0.005 per run. One result = one
profile row or one post. Platform usage (compute, proxy) is included.

| Apify plan | Price per 1,000 results |
|---|---|
| Free | $2.50 |
| Starter (Bronze) | $2.00 |
| Scale (Silver) | $1.75 |
| Business (Gold) and above | $1.50 |

1,000 profiles cost **$2.50** on the Free plan and **$1.50** on Business. Accounts that don't exist are free.

### Use it from AI agents (Claude, ChatGPT, Cursor and other MCP clients)

Add `https://mcp.apify.com/?tools=alom/threads-profile-scraper` as a connector (Claude: Settings → Connectors → Add
custom connector; Claude Code: `claude mcp add --transport http threads-profiles "https://mcp.apify.com/?tools=alom/threads-profile-scraper"`)
and sign in with your Apify account. Then ask, for example: *"Compare the followers and bios of @zuck, @mosseri and
@nasa."*

### Limitations

- **No follower or following lists, and no following count:** Threads doesn't show them to logged-out visitors.
- An unknown username is named in the run's status message and is not charged; the rest of the run is delivered.

### FAQ

**Do I need a Threads or Instagram account?** No. Nothing is logged in, so there is nothing to ban.

**Where do the e-mails come from?** Only from the public bio: if a person wrote an address there, it is in `emails`.
Nothing is guessed or looked up elsewhere.

**Is it legal?** The Actor collects only what Threads shows publicly without login. Profiles are personal data: check
that your use has a lawful basis (GDPR and similar laws), especially before you contact anyone.

### More scrapers from the same developer

- [Threads Scraper](https://apify.com/alom/threads-scraper): posts, profiles, replies, reposts, keyword and hashtag search, account search
- [Threads Search Scraper](https://apify.com/alom/threads-search-scraper): posts by keyword or #hashtag, top or newest first, with filters
- [Threads Account Finder](https://apify.com/alom/threads-lead-finder): Threads accounts by keyword with followers, bio links and the contacts they list
- [Threads Replies Scraper](https://apify.com/alom/threads-replies-scraper): the replies under any Threads post with whole reply threads
- [Threads Hashtag & Keyword Monitor](https://apify.com/alom/threads-keyword-monitor): only the new posts for your keywords and #hashtags, for scheduled runs
- [YouTube Channel Scraper](https://apify.com/alom/youtube-channel-scraper): every video of a channel with views, likes, dates and channel stats

### Feedback

Missing a field, found a bug, or need a feature? Open an issue in the **Issues** tab and I'll take a look. If this
Actor saved you time, a short review on the Store page helps other people find it.

# Actor input Schema

## `usernames` (type: `array`):

e.g. <code>zuck</code>, <code>@mosseri</code> or <code>https://www.threads.com/@nasa</code> (threads.net works too).

## `includePosts` (type: `boolean`):

Off: one profile row per account (followers, bio, bio links, e-mails, verification) - one request each, fast. On: the profile row plus the account's latest posts, up to <i>Max posts per account</i>.

## `maxPosts` (type: `integer`):

Only used when <i>Also get their latest posts</i> is on. Logged out, Threads pages through a few hundred posts of an account.

## `postedAfter` (type: `string`):

Only posts published after this date (UTC), ISO timestamp or relative like <code>30 days</code>. Paging stops once older posts are reached.

## `minLikes` (type: `integer`):

Keep only posts with at least this many likes. Leave empty for no limit. Handy for search, where many results have no engagement at all.

## `languages` (type: `array`):

Keep only posts in these languages, as two-letter codes: <code>en</code>, <code>es</code>, <code>pt</code>, <code>fr</code>, <code>de</code>, <code>ja</code>, <code>ko</code>, <code>zh</code>, <code>ru</code>… The language is guessed from the text of each post (see the <code>language</code> field). Posts too short to tell are kept.

## `includeViews` (type: `boolean`):

Fill <code>viewCount</code> (the number Threads shows under a post, e.g. 423K views) on every post. Each count is read from the post's own page: one extra request per post, so the run takes longer. Not charged extra. A post you give by URL always has its view count.

## `maxConcurrency` (type: `integer`):

Profiles / posts / keywords processed in parallel.

## `proxyConfiguration` (type: `object`):

The default Apify datacenter proxy works and is included in the price. If Threads starts blocking it, the run switches to residential proxies by itself (logged).

## Actor input object example

```json
{
  "usernames": [
    "zuck",
    "mosseri",
    "nasa"
  ],
  "includePosts": false,
  "maxPosts": 20,
  "includeViews": false,
  "maxConcurrency": 3,
  "proxyConfiguration": {
    "useApifyProxy": true
  }
}
```

# Actor output Schema

## `results` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "usernames": [
        "zuck",
        "mosseri",
        "nasa"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("alom/threads-profile-scraper").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "usernames": [
        "zuck",
        "mosseri",
        "nasa",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("alom/threads-profile-scraper").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "usernames": [
    "zuck",
    "mosseri",
    "nasa"
  ]
}' |
apify call alom/threads-profile-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,alom/threads-profile-scraper"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/v9az3c9yHG7WxTikK/builds/4qD7UNVntq7f2QalD/openapi.json