# Threads Public Intelligence API (`soilair/threads-public-intelligence-api`) Actor

Scrape public Threads profile posts and keyword-search results without login. Get text, authors, timestamps, engagement metrics, media, hashtags, mentions, and canonical post URLs with resilient SSR routing.

- **URL**: https://apify.com/soilair/threads-public-intelligence-api.md
- **Developed by:** [Salih Can Kurnaz](https://apify.com/soilair) (community)
- **Categories:** Social media, Lead generation, AI
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $2.90 / 1,000 threads post 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

## Threads Public Intelligence API

Extract public Threads posts from profile usernames and keyword searches without login or external API keys.

### What it returns

Each Dataset row is a contentful public Threads post with:

- source mode and target
- exact source URL
- post ID and short code
- canonical Threads post URL
- post text
- timestamp
- likes, replies, reposts, quotes, and views when publicly available
- reply flag
- author ID, username, full name, verified status, and avatar
- media URLs
- hashtags and mentions
- scrape timestamp

### Input

```json
{
  "profiles": ["zuck", "nasa"],
  "searchQueries": ["artificial intelligence"],
  "maxResultsPerTarget": 12,
  "enableResidentialFallback": false
}
```

You can provide profiles, searches, or both.

### Reliability

Production routing is automatic:

1. direct public Threads SSR
2. on HTTP 403/429, open a circuit breaker for the blocked direct egress
3. rotate through Apify datacenter proxy
4. optionally use Residential-US only as a last resort when enabled

The Actor does not use browser automation, login cookies, anonymous GraphQL persisted queries, or third-party scraping APIs.

### Data-quality rules

- only contentful posts are saved
- deterministic per-target deduplication
- exact profile/search source target retained
- canonical Threads URL when public username and post code are available
- engagement fields are returned only when publicly present
- no fabricated metrics

### Pricing

Pay per event:

- `threads-post`
  - FREE: **$0.0032/post**
  - BRONZE: **$0.0031/post**
  - SILVER: **$0.0030/post**
  - GOLD / PLATINUM / DIAMOND: **$0.0029/post**
- `threads-target`: **$0.0005** per successfully processed profile or search target
- `apify-actor-start`: **$0.00005**
- minimum run spending limit: **$0.20**

The Actor reads the run's pay-per-event spending limit and conservatively bounds the number of accepted targets using the FREE-tier worst case before starting work.

### Notes

Threads is a live social platform. Search results and engagement counts can change between runs. Public logged-out surfaces can also apply temporary rate limits; the Actor's automatic egress fallback is designed for this case.

# Actor input Schema

## `profiles` (type: `array`):

Public Threads usernames without @, for example zuck, nasa, or instagram.

## `searchQueries` (type: `array`):

Public Threads keyword searches, for example artificial intelligence or climate tech.

## `maxResultsPerTarget` (type: `integer`):

Maximum number of contentful post rows retained for each profile or search target.

## `enableResidentialFallback` (type: `boolean`):

Optional last-resort reliability mode. Direct SSR and datacenter rotation are tried first; Residential-US is used only after blocking or transport failure.

## Actor input object example

```json
{
  "profiles": [
    "zuck",
    "nasa"
  ],
  "searchQueries": [
    "artificial intelligence"
  ],
  "maxResultsPerTarget": 12,
  "enableResidentialFallback": false
}
```

# Actor output Schema

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

No description

## `summary` (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 = {};

// Run the Actor and wait for it to finish
const run = await client.actor("soilair/threads-public-intelligence-api").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 = {}

# Run the Actor and wait for it to finish
run = client.actor("soilair/threads-public-intelligence-api").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 '{}' |
apify call soilair/threads-public-intelligence-api --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,soilair/threads-public-intelligence-api"
        }
    }
}
```

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/VuhmchGb3ak8RWfM2/builds/ZOYb2yhEbzflHmwaS/openapi.json