# Threads Profile Scraper - Public Account Data (`thenetaji/threads-profile-scraper`) Actor

Get any public Threads account by username: bio, follower count, verification, avatar and topic tags. No Threads login or account needed.

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

## Pricing

from $3.40 / 1,000 profiles

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?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
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.
Actors are written with capital "A".

## 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.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Threads Profile Scraper

The Actor retrieves one public Threads account by username and returns its profile record: display name, bio, follower count, verification, avatar, and the topic tags Threads shows on the account. It accepts a bare username, an `@handle`, or a full profile URL.

### Accepted input

| Field | Type | Default | Description |
|---|---|---|---|
| `username` | string | required | A Threads username, `@handle`, or full profile URL, e.g. `instagram`, `@instagram`, or `https://www.threads.com/@instagram`. |

```json
{
  "username": "zuck"
}
```

### Response fields

| Field | Contents |
|---|---|
| `user_id` | Threads' own numeric ID for the account, as a string |
| `username` | The account's Threads username |
| `requested_username` | The value this run asked for, echoed back |
| `full_name` | The account's display name |
| `biography` | The account's bio, plain text |
| `follower_count` | Followers, read at the moment of the request |
| `is_verified` | Whether the account carries Threads' verification mark |
| `is_private` | Whether the account is private |
| `profile_pic_url` | The account's avatar |
| `hd_profile_pic_versions` | The avatar at larger sizes, each an object with `url`, `width` and `height` |
| `bio_links` | Links in the account's bio |
| `profile_tags` | The topic tags Threads shows on the profile, republished whole |
| `raw` | The complete profile record exactly as Threads' own internal API returns it |

```json
{
  "user_id": "63055343223",
  "username": "zuck",
  "full_name": "Mark Zuckerberg",
  "biography": "Mostly superintelligence and MMA takes",
  "follower_count": 5723633,
  "is_verified": true,
  "is_private": false
}
```

### The `raw` field

Threads publishes no documented schema for this data — the fields above are the ones consistently present and worth a column of their own, pulled from a record that, measured live, carries several dozen fields, some of them internal (`gating`, `transparency_label`, podcast metadata that is null on non-podcast accounts). Everything not listed in the table above is still in the row, inside `raw`, exactly as Threads returned it. A field missing from the table today is not missing from the data.

### Behaviour on an account that cannot be resolved

A username, handle, or URL that does not resolve to a real account finishes the run with an empty dataset rather than failing it — this covers both a deleted account and one that was never a Threads account at all. The distinction is not exposed, since Threads itself does not expose it consistently: what Threads answers for "never existed" and for "deleted" is not the same response every time, and this Actor treats both as one outcome rather than guessing between them.

### Frequently asked questions

**Why is `follower_count` slightly different if I run this twice?**
It is a live counter, read at request time. Two runs minutes apart on a fast-growing account will disagree, and that is drift rather than a fault.

**What is the difference between `biography` and the bio shown in `raw`?**
`biography` is the plain-text bio. Threads also carries a richer, structured version of the same text internally (with mention and link fragments broken out); that structured form is available in `raw` for a caller who needs the fragments rather than the flat string.

**Why is `profile_tags` sometimes `null`?**
Not every account has topic tags attached. `null` means the account carries none, not that the field failed to load.

**Can I look up several accounts in one run?**
Each run takes one username. For a list, run the Actor once per username, or drive it from a task with different input each time.

### Related

[Threads Posts Scraper](https://apify.com/thenetaji/threads-posts-scraper) exports an account's public posts by `user_id` — the exact value this Actor returns. [Threads Post Scraper](https://apify.com/thenetaji/threads-post-scraper) fetches one post by its link. [Threads Search Scraper](https://apify.com/thenetaji/threads-search-scraper) finds public posts by keyword.

# Actor input Schema

## `username` (type: `string`):

A Threads username, @handle, or full profile URL -- e.g. "zuck", "@zuck", or https://www.threads.com/@zuck. Any of the three works.

## Actor input object example

```json
{
  "username": "instagram"
}
```

# Actor output Schema

## `dataset` (type: `string`):

All records scraped by this run

# 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 = {
    "username": "zuck"
};

// Run the Actor and wait for it to finish
const run = await client.actor("thenetaji/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 = { "username": "zuck" }

# Run the Actor and wait for it to finish
run = client.actor("thenetaji/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 '{
  "username": "zuck"
}' |
apify call thenetaji/threads-profile-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,thenetaji/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/cnTrZ4tMbR65cdkgK/builds/GhTU8IcJd9TbGFYXi/openapi.json