# Threads (Meta) Scraper (`cravl/threads-scraper`) Actor

Scrape Meta Threads profiles and posts in guest mode: profiles with exact follower counts and bio, posts with caption, like/reply/repost counts, and replies. No login required.

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

## Pricing

$1.00 / 1,000 records

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

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 (Meta) Scraper

Scrape Meta Threads profiles and posts in guest mode: no login.

#### What you get

- **Profiles**: username, full name, bio, exact follower count, threads count, recent timeline posts
- **Posts**: caption text, like/reply/repost counts, timestamp, author verification, and the reply tree

#### How it works

The engine re-fetches the raw server response (threads.net 30x-redirects to threads.com), walks the embedded Instagram-style post objects with a balanced-brace JSON scan, and merges the rendered-DOM state.

#### Input

| Field | Type | Description |
|---|---|---|
| `directUrls` | array | Profile URLs (threads.net/@user) and/or post permalinks |
| `proxyConfiguration` | object | Apify proxy settings |

#### Output

Profile records: `username`, `fullName`, `biography`, `followersExact`, `timeline[]`.
Post records: `url`, `username`, `text`, `likes`, `replies`, `reposts`, `takenAt`, `repliesList[]`, `repliesTotal`.

#### Use cases

- Threads profile monitoring with exact follower counts
- Post engagement tracking (likes/replies/reposts)
- Reply-thread extraction for conversation analysis

### Migrating from other Apify Actors

Cravl Actors accept Apify-style inputs and emit familiar field names alongside Cravl-specific fields, so most pipelines migrate with minimal changes.

#### Input compatibility

- `startUrls` (array of URLs, or objects with a `url` key) is accepted as an alias for `directUrls`.

#### Output compatibility

Post URLs emit one item with added aliases: `likeCount`, `replyCount`, `retweetCount`, `postedAt`, `inputUrl`. Profile URLs emit one profile item (record `profile`) followed by one item per timeline post (record `post`) with `profileUrl` and `profileUsername` context.

# Actor input Schema

## `directUrls` (type: `array`):

Threads profile URLs (threads.net/@user) and post permalinks (threads.net/@user/post/CODE).

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

Residential proxies recommended where the site gates guest access by exit IP reputation.

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

Optional alias for directUrls, accepted for compatibility with common Apify Actor inputs. Items may be URLs or objects with a url key.

## Actor input object example

```json
{
  "directUrls": [
    "https://www.threads.net/@nasa"
  ]
}
```

# Actor output Schema

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

The default dataset contains the extracted 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 = {
    "directUrls": [
        "https://www.threads.net/@nasa"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("cravl/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 = { "directUrls": ["https://www.threads.net/@nasa"] }

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

```

## MCP server setup

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