# Threads Scraper (`anyxsolutions/threads-scraper`) Actor

Scrapes public Threads profiles and posts: follower counts, bios, and the latest threads with text, likes, replies, images and videos, from a profile or post URL.

- **URL**: https://apify.com/anyxsolutions/threads-scraper.md
- **Developed by:** [Anyx Solutions](https://apify.com/anyxsolutions) (community)
- **Categories:**
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $4.90 / 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?

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

![banner](<run ./scripts/banner.sh to generate>)

## Threads Scraper

**Public Threads profiles and posts as clean JSON — followers, bios, latest threads, replies, likes, images and videos.**

Scrapes public Threads profiles and posts: follower counts, bios, and the latest threads with text, likes, replies, images and videos, from a profile or post URL. Give it a profile URL and it returns the account plus its most recent threads; give it a post URL and it returns the post plus the replies under it. Built for social-listening teams, creator-economy analysts, brand monitors and researchers who need Threads data without a Meta login.

### ⚡ Quick start

```json
{ "startUrls": [{ "url": "https://www.threads.net/@zuck" }], "maxItems": 5 }
```

### 🧩 Input

| Field | Type | Required | Default | Description |
|---|---|---|---|---|
| `startUrls` | array | yes | — | Threads profile or post URLs to scrape, e.g. `https://www.threads.net/@zuck` (profile plus latest threads) or `https://www.threads.net/@zuck/post/C8CTu0iswgv` (post plus replies). Both threads.net and threads.com links are accepted. |
| `usernames` | array | no | — | Threads handles to scrape as profiles, with or without the leading `@`, e.g. `zuck` or `@meta`. Each one is treated like a profile start URL. |
| `maxItems` | integer | no | `5` | Maximum number of dataset items per start URL. For a profile this is the profile item plus its latest threads; for a post it is the post plus its replies. |
| `proxyConfiguration` | object | no | `{ "useApifyProxy": true }` | Apify proxy settings used for the run. Datacenter proxies are enough for public Threads pages; switch to residential if runs start hitting the login wall. |

Supported start URLs:

- `https://www.threads.net/@<username>` — the profile and its latest threads
- `https://www.threads.net/@<username>/post/<code>` — one post and its replies
- `https://www.threads.net/t/<code>` — one post and its replies (short link)

### 📤 Output

Every row carries an `itemType` of either `profile` or `thread`. A profile start URL yields one `profile` row followed by `thread` rows; a post start URL yields the post as a `thread` row followed by its replies, which are marked with `isReply: true` and point back via `parentCode`. Fields that only apply to one type are absent on the other.

#### Fields

| Field | Type | Description |
|---|---|---|
| `itemType` | string | `profile` or `thread`. |
| `url` | string | Public URL of the profile or post. |
| `username` | string | Handle of the account (profile) or the post author (thread). |
| `is_private` | boolean | Profile only. Whether the account is private. |
| `is_verified` | boolean | Profile only. Whether the account carries a verified badge. |
| `profile_pic` | string | Profile only. URL of the profile picture. |
| `full_name` | string | Profile only. Display name. |
| `bio` | string | Profile only. Biography text. |
| `bio_links` | array | Profile only. External links in the bio. |
| `followers` | integer | Profile only. Follower count. |
| `text` | string | Thread only. Post text. |
| `published_on` | integer | Thread only. Unix timestamp (seconds) when the post was published. |
| `id` | string | Thread only. Full post id (`<pk>_<user_pk>`). |
| `pk` | string | Thread only. Numeric post id. |
| `code` | string | Thread only. Short code used in the post URL. |
| `user_pic` | string | Thread only. Author profile picture URL. |
| `user_verified` | boolean | Thread only. Whether the author is verified. |
| `user_pk` | string | Thread only. Author numeric id. |
| `user_id` | string | Thread only. Author id. |
| `has_audio` | boolean | Thread only. Whether an attached video has audio. |
| `reply_count` | integer | Thread only. Number of direct replies. |
| `like_count` | integer | Thread only. Number of likes. |
| `images` | array | Thread only. Image URLs attached to the post. |
| `image_count` | integer | Thread only. Number of attached images. |
| `videos` | array | Thread only. Video URLs attached to the post. |
| `isReply` | boolean | Thread only. `true` when the row is a reply collected from a post URL. |
| `parentCode` | string | Thread only. Short code of the post a reply belongs to. |
| `repostCount` | integer | Thread only. Number of reposts. |
| `quoteCount` | integer | Thread only. Number of quote posts. |

<details><summary>Example output</summary>

```json
[
  {
    "itemType": "profile",
    "is_private": false,
    "is_verified": true,
    "profile_pic": "https://scontent.cdninstagram.com/v/t51.2885-19/....jpg",
    "username": "natgeo",
    "full_name": "National Geographic",
    "bio": "Inspiring the explorer in everyone 🌎",
    "bio_links": ["https://on.natgeo.com/instagram"],
    "followers": 16860620,
    "url": "https://www.threads.net/@natgeo"
  },
  {
    "itemType": "thread",
    "text": "How could we pick just one?",
    "published_on": 1761570184,
    "id": "3752645156739608236_63269174602",
    "pk": "3752645156739608236",
    "code": "DQUEuM_je6s",
    "username": "natgeo",
    "user_pic": "https://scontent.cdninstagram.com/v/t51.2885-19/....jpg",
    "user_verified": true,
    "user_pk": "63269174602",
    "user_id": "63269174602",
    "has_audio": null,
    "reply_count": 11,
    "like_count": 53,
    "images": null,
    "image_count": 0,
    "videos": [],
    "url": "https://www.threads.net/@natgeo/post/DQUEuM_je6s",
    "isReply": false,
    "parentCode": null,
    "repostCount": 4,
    "quoteCount": 2
  }
]
```

</details>

### 💡 Use cases

- Track follower growth and engagement of brands, creators and competitors on Threads.
- Collect replies under a post for sentiment analysis and community research.
- Archive an account's latest threads, images and videos for reporting.
- Feed Threads posts into social-listening dashboards alongside other networks.

### ❓ FAQ

- **Do I need a proxy?** The Actor defaults to Apify datacenter proxies, which are enough for public profiles and posts. If runs start hitting a login wall, switch `proxyConfiguration` to a residential group.
- **Do I need a Threads account?** No. Only public profiles and posts are scraped, without logging in.
- **How many results can I get?** `maxItems` caps rows per start URL (the profile row counts as one). Threads shows only the most recent handful of posts on a profile without logging in, so a profile typically yields up to about ten threads; post pages return the post plus its visible replies. Add more start URLs or `usernames` to widen coverage.
- **Can I use threads.com links?** Yes. Threads moved to threads.com; both threads.net and threads.com URLs are accepted.
- **Why did a run return fewer items than expected?** Private accounts, deleted posts and very short feeds yield fewer rows. If a public page returns nothing, the site may have changed its layout — open an issue and we will update the Actor.

### 🔗 More scrapers by Anyx

- [X (Twitter) Scraper](https://apify.com/anyxsolutions/x-twitter-scraper)
- [Bluesky Scraper](https://apify.com/anyxsolutions/bluesky-scraper)
- [Reddit Scraper](https://apify.com/anyxsolutions/reddit-scraper)
- [TikTok Trending Hashtags Scraper](https://apify.com/anyxsolutions/tiktok-trending-hashtags-scraper)

### 🤝 Anyx Solutions

We build custom scrapers and data-extraction pipelines.

- Email: tantosthor@gmail.com

### 🖼 Image credit

Image credit: [threads.net](https://www.threads.net/)

# Actor input Schema

## `startUrls` (type: `array`):

Threads profile or post URLs to scrape, e.g. https://www.threads.net/@zuck (profile plus latest threads) or https://www.threads.net/@zuck/post/C8CTu0iswgv (post plus replies). Both threads.net and threads.com links are accepted.

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

Threads handles to scrape as profiles, with or without the leading @, e.g. zuck or @meta. Each one is treated like a profile start URL.

## `maxItems` (type: `integer`):

Maximum number of dataset items per start URL. For a profile this is the profile item plus its latest threads; for a post it is the post plus its replies.

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

Apify proxy settings used for the run. Datacenter proxies are enough for public Threads pages; switch to residential if runs start hitting the login wall.

## Actor input object example

```json
{
  "startUrls": [
    {
      "url": "https://www.threads.net/@zuck"
    },
    {
      "url": "https://www.threads.net/@meta"
    }
  ],
  "usernames": [],
  "maxItems": 5,
  "proxyConfiguration": {
    "useApifyProxy": true
  }
}
```

# Actor output Schema

## `overview` (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 = {
    "startUrls": [
        {
            "url": "https://www.threads.net/@zuck"
        },
        {
            "url": "https://www.threads.net/@meta"
        }
    ],
    "usernames": []
};

// Run the Actor and wait for it to finish
const run = await client.actor("anyxsolutions/threads-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 = {
    "startUrls": [
        { "url": "https://www.threads.net/@zuck" },
        { "url": "https://www.threads.net/@meta" },
    ],
    "usernames": [],
}

# Run the Actor and wait for it to finish
run = client.actor("anyxsolutions/threads-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 '{
  "startUrls": [
    {
      "url": "https://www.threads.net/@zuck"
    },
    {
      "url": "https://www.threads.net/@meta"
    }
  ],
  "usernames": []
}' |
apify call anyxsolutions/threads-scraper --silent --output-dataset

```

## MCP server setup

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