# Threads Profile Posts Scraper (`plummy_bookbag/threads-profile-scraper`) Actor

Scrape all posts of Threads profiles back to a date, with likes, shares, replies, reposts, quotes, view counts, post type and media URLs. Uses an authenticated threads.com session.

- **URL**: https://apify.com/plummy\_bookbag/threads-profile-scraper.md
- **Developed by:** [Mark Pandit](https://apify.com/plummy_bookbag) (community)
- **Stats:** 1 total users, 1 monthly users, 75.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $2.00 / 1,000 results

This Actor is paid per event and usage. You are charged both the fixed price for specific events and for Apify platform usage.

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 Posts Scraper

Collect public posts from one or more Threads profiles, including engagement metrics, media links, post type, timestamps, and view counts when available.

Results are saved continuously while the Actor runs, so you can begin reviewing or exporting data before every profile finishes.

### What you get

For each post, the Actor can return:

- Post text, URL, ID, code, and publication time
- Post type: video, photo, carousel, text, reply, quote, or repost
- Likes, replies, reposts, quotes, and shares
- Public view or play count when Threads exposes it
- A combined engagement total
- Author name, username, and verification status
- Media URLs and audio availability
- A date-range flag for filtering results

Every dataset row is a post. Profile progress and completion summaries appear only in the run log.

### Quick start

1. Open the Actor input form.
2. Enter one Threads profile per line.
3. Choose the earliest date to scrape.
4. Set the per-profile and total run limits.
5. Click **Start**.
6. Open the **Output** tab to watch records arrive.

Example profile input:

```text
https://www.threads.com/@example_account
@example_second_account
```

Full profile URLs, `@handles`, and bare usernames are accepted.

### Input

| Field | Description | Default |
|---|---|---:|
| **Profiles** | One Threads profile URL or username per line | One sample profile |
| **Scrape till date** | Earliest date to include, in `YYYY-MM-DD` format | `2026-09-10` |
| **Max posts per profile** | Maximum records collected from one profile | `100` |
| **Max posts for the entire run** | Maximum post records collected across all profiles | `3000` |

#### Date behavior

The Actor starts with the newest posts and works backward. It stops after reaching posts older than **Scrape till date**.

Because Threads returns posts in pages, the last page can contain a small number of older records. Use `in_date_range = true` to select only posts published on or after the requested date.

#### Limits

Both limits apply:

- **Max posts per profile** prevents one profile from using the entire run allowance.
- **Max posts for the entire run** stops collection after the combined post count reaches the requested total. Remaining profiles are skipped.

### Output

The default dataset contains only post records.

Important fields include:

| Field | Meaning |
|---|---|
| `username` | Requested profile username |
| `post_url` | Public Threads post URL |
| `taken_at_utc` | Publication time in UTC |
| `text` | Post text or caption |
| `post_type` | Normalized post type |
| `view_count` | Public view or play count, when available |
| `view_count_status` | `available` or `unavailable` |
| `like_count` | Likes |
| `reply_count` | Direct replies |
| `repost_count` | Reposts |
| `quote_count` | Quote posts |
| `share_count` | Shares |
| `engagement_total` | Likes + replies + reposts + quotes + shares |
| `media_urls` | Media URLs, separated by `|` when multiple are present |
| `in_date_range` | Whether the post is on or after the requested date |

### View-count availability

Threads does not publish view counts for every post. When no public count is available:

- `view_count` is empty
- `view_count_status` is `unavailable`

This does not mean the post has zero views.

### Export and integration

Use the **Output** tab to:

- Download JSON, CSV, Excel, XML, or RSS
- Filter and select dataset fields
- Access results through the Apify API
- Connect the dataset to automation tools and cloud storage

Results are streamed page by page instead of waiting for an entire profile to finish.

### Responsible use

This Actor collects publicly visible Threads profile and post data. Use the results in accordance with applicable laws, privacy requirements, and the platform's terms. Avoid collecting or using personal data without a lawful purpose.

### Notes

- Deleted, private, restricted, or unavailable content may not be returned.
- Counts can change between requests because engagement continues after collection.
- Media URLs may expire and should be downloaded promptly if long-term storage is required.
- Platform changes or temporary rate limits can affect availability.

# Actor input Schema

## `profiles` (type: `string`):

One profile per line — full URL (https://www.threads.com/@user) or bare @handle/username.

## `scrapeTillDate` (type: `string`):

Lower date boundary from the latest post. Posts on/after this date are flagged in\_date\_range. Scraping stops once posts get older than this date.

## `maxPostsPerProfile` (type: `integer`):

Record cap per profile. Stops that profile's scraping when reached.

## `maxPostsPerRun` (type: `integer`):

Total record cap for the whole run. When hit, remaining profiles are skipped and the run ends.

## Actor input object example

```json
{
  "profiles": "https://www.threads.com/@the.indian.angle\nhttps://www.threads.com/@ek.gaon.wala",
  "scrapeTillDate": "2026-09-10",
  "maxPostsPerProfile": 100,
  "maxPostsPerRun": 3000
}
```

# Actor output Schema

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

The default dataset containing scraped post records.

# 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 = {
    "profiles": `https://www.threads.com/@the.indian.angle
https://www.threads.com/@ek.gaon.wala`
};

// Run the Actor and wait for it to finish
const run = await client.actor("plummy_bookbag/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 = { "profiles": """https://www.threads.com/@the.indian.angle
https://www.threads.com/@ek.gaon.wala""" }

# Run the Actor and wait for it to finish
run = client.actor("plummy_bookbag/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 '{
  "profiles": "https://www.threads.com/@the.indian.angle\\nhttps://www.threads.com/@ek.gaon.wala"
}' |
apify call plummy_bookbag/threads-profile-scraper --silent --output-dataset

```

## MCP server setup

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