New: the Scrapier MCP server. Every scraper in Claude Code with one command. See how →
GET/api/v2/threads-user-posts/

Threads User Posts Scraper API

Last updated: · REST · JSON

Quick answer

Send GET https://proxy.scrapier.io/api/v2/threads-user-posts/?usernames=zuck with your key in the X-API-Key header. You get the page of posts back as JSON. 1 credit per page of posts; failed calls are free.

  • 1 credit per page of posts
  • Failed calls free
  • 3 parallel requests per key
Copy for your AI agent
API

Call the Threads User Posts Scraper API

Use the Threads User Posts Scraper API from your own apps, scripts or agents. You need a Scrapier account and the API key from your dashboard. Pick a language.

posts.py
import requests# Replace YOUR_API_KEY with the key from your Scrapier dashboardAPI_KEY = "YOUR_API_KEY"params = {    "usernames": "zuck",}r = requests.get(    "https://proxy.scrapier.io/api/v2/threads-user-posts/",    headers={"X-API-Key": API_KEY},    params=params,    timeout=210,)r.raise_for_status()# The result sits under data.postsresult = r.json()["data"]["posts"]print(result)

Threads User Posts Scraper API in Python

Plain requests is all you need — no SDK. Every response is typed JSON.

Install

$ pip install requests

Other ways to call it

Playground

Threads User Posts Scraper API Interactive Playground

Edit the request, watch the code update, then run it. Without a key it shows the catalog sample and bills nothing. With your key it makes a real call from your browser; the key goes only to proxy.scrapier.io and is never stored.

@
No key? Run the catalog sample.
ReadyLatency —Credits billed: 0
Request readyGET /api/v2/threads-user-posts/?usernames=zuck

Press Run request to send it. Without a key you get the catalog sample.

Sending request…
Error

Failed calls are not billed.

Import in PostmanOpenAPI spec

The sample is the same for every input: it shows the response shape, not the account you typed.

Example response, catalog sample from 9 Nov 2026
{
  "success": true,
  "data": {
    "username": "zuck",
    "page": 1,
    "page_size": 25,
    "posts": [
      {
        "username": "zuck",
        "id": "3920731152608519405_63055343223",
        "code": "DZpPDXbCeTt",
        "caption": "500M monthly actives on Threads in less than 3 years.",
        "like_count": 17686,
        "taken_at": "2026-06-16 10:59:56",
        "url": "https://www.threads.net/@zuck/post/DZpPDXbCeTt",
        "input_username": "zuck",
        "scraped_at": "2026-06-20T12:00:00.000Z"
      }
    ],
    "next_cursor": "eyJ1IjoienVjayIsImEiOiJBQUFceDNkIiwicCI6Mn0"
  }
}
Data

Data You Can Extract

Threads User Posts Scraper reads the posts of one public Threads account. Every field below comes from the catalog sample response, as typed JSON.

Post

5 fields in the response.

  • id
  • code
  • url
  • caption
  • taken_at

Engagement

1 field in the response.

  • like_count

Author and input

2 fields in the response.

  • username
  • input_username

Timing

1 field in the response.

  • scraped_at

Response envelope and paging

5 fields in the response.

  • success
  • data.username
  • data.page
  • data.page_size
  • data.next_cursor
Schema

Response Schema Reference

Every field in the sample response. Field names stay the same on every call.

FieldTypeExampleDescription
posts.idstring"3920731152608519405_63055343223"Post ID
posts.codestring"DZpPDXbCeTt"Short post code used in the URL
posts.urlstring"https://www.threads.net/@zuck/post/DZpPDXbC…"URL of the post
posts.captionstring"500M monthly actives on Threads in less tha…"Text of the post
posts.taken_atstring"2026-06-16 10:59:56"When the post was published
posts.like_countinteger17686Number of likes
posts.usernamestring"zuck"Handle of the author
posts.input_usernamestring"zuck"The usernames value you sent
posts.scraped_atstring"2026-06-20T12:00:00.000Z"When Scrapier read the post (ISO 8601)
successbooleantruetrue on every 200 response
data.usernamestring"zuck"The account you asked for
data.pageinteger1Page number of this response
data.page_sizeinteger25Number of posts on this page
data.next_cursorstring"eyJ1IjoienVjayIsImEiOiJBQUFceDNkIiwicCI6Mn0"Pass back as cursor for the next page; null on the last page
Parameters

Request Parameters Reference

NameTypeRequiredDefaultDescriptionExample
usernamesstringYes—A Threads username. One per call. Required on the first call, ignored when cursor is set. Aliases: username, user, query, qzuck
cursorstringNo—Pass back data.next_cursor from the previous response to get the next page; null means the last page—
use_proxybooleanNotrueUse Scrapier's residential proxy pool when true (default true). Leave as istrue
raw_databooleanNofalseReturn the raw upstream payload under raw_responses instead of the formatted poststrue

One value per call: to read ten accounts, make ten calls and page each with cursor. Booleans are the strings true or false.

Pagination in the Threads User Posts Scraper API

The Threads User Posts Scraper API returns results in pages. Pass data.next_cursor back as cursor to get the next page; when it is null there are no more. Each successful call, first page or later, costs 1 credit.

Access

Access Without Threads Login

The Threads User Posts Scraper API needs no Threads account, no login and no session cookies. You send your Scrapier key in the X-API-Key header and get JSON back. It reads public data only: what any visitor sees without logging in.

Performance

Speed, Cost and Concurrency

MetricValueSource
Cost of a successful call1 creditScrapier catalog
Cost of a failed call0 creditsAny non-2xx response
Parallel requests per key3Above that: 429 with Retry-After
Recommended client timeout210 secondsScrapier docs, every endpoint

Latency of the Threads User Posts Scraper API

Scrapier does not publish a latency or success-rate figure for this endpoint. Each call reads Threads at call time, so response time depends on Threads and on the size of the result. Set a client timeout of 210 seconds, as the docs recommend for every endpoint.

Limits

Limits of the Endpoint

Honest constraints of the Threads User Posts Scraper API.

  • Public data only.
  • A failed call, for example a missing or unavailable page of posts, returns a non-2xx status and costs 0 credits.
  • Data is read live at call time.
  • 3 parallel requests per key; above that the API answers 429 with Retry-After.
  • Large results come in pages; pass data.next_cursor back as cursor.
  • Fields Threads does not show are not returned.
Compare

Scrapier vs the Official Threads API

The official Threads API is the better choice when you publish posts, manage replies or act on behalf of an account you own.

FeatureScrapier page of posts scraperOfficial Threads API
Access neededOne Scrapier API keyA Meta developer app, access tokens and the permissions Meta grants
Which dataAn account's posts, a page at a timeDepends on the endpoints and permissions available to your app
Fields returned9 fields, as in the catalog sampleDepends on the fields you request
Rate limitsUp to 3 parallel requests per key; 429 with Retry-AfterLimits set by Meta per app
SetupSign up, copy a key, send a requestCreate an app, set up OAuth, manage tokens
Cost1 credit per call, from $1.20 per 1,000 callsSet by Meta's terms
Errors

Errors and Retry Handling

StatusMeaningBilledFix
200Page of posts data returned in data.postsYes—
400Bad or missing inputNoCheck usernames: one value per call
401X-API-Key header missingNoAdd the header
402Out of credits (body has balance)NoTop up; retrying will not help
403Invalid or revoked API keyNoCheck the key in your dashboard
429ThrottledNoWait Retry-After seconds, then retry
5xxUpstream failure or timeoutNoRetry with backoff; set a 210 s client timeout

From the error reference. Any non-2xx response costs 0 credits.

Retry logic for the Threads User Posts Scraper API

retry.py
import time, requests

def get_posts(value, key, tries=5):
    for attempt in range(tries):
        r = requests.get(
            "https://proxy.scrapier.io/api/v2/threads-user-posts/",
            headers={"X-API-Key": key},
            params={"usernames": value},
            timeout=210,
        )
        if r.status_code == 429:
            time.sleep(int(r.headers.get("Retry-After", 2 ** attempt)))
        elif r.status_code >= 500:
            time.sleep(2 ** attempt)
        else:
            r.raise_for_status()
            return r.json()
    raise RuntimeError("gave up after retries")
Pricing

Pricing and Rate Limits

PlanMonthly pricePages Of Posts includedCost per 1,000
Hobby$2915,000$1.93
Pro$7950,000$1.58
Scale$299250,000$1.20

See all plans →

Billing rules for the Threads User Posts Scraper API

The Threads User Posts Scraper API bills 1 credit per successful page of posts. Failed calls, meaning any non-2xx status, cost 0 credits. Every plan allows 3 parallel requests per key. The free tier lets you try it before you pay.

Bulk

Bulk Lookups and CSV

usernames takes one value per call. For a list, loop and run up to 3 requests in parallel per key, then flatten each row into one CSV line.

bulk.py
import csv, requests
from concurrent.futures import ThreadPoolExecutor

values = ["zuck"]  # your list

def fetch(value):
    r = requests.get(
        "https://proxy.scrapier.io/api/v2/threads-user-posts/",
        headers={"X-API-Key": "YOUR_API_KEY"},
        params={"usernames": value},
        timeout=210,
    )
    r.raise_for_status()
    out = r.json()["data"]["posts"]
    return out if isinstance(out, list) else [out]

# 3 parallel requests per key is the limit
with ThreadPoolExecutor(max_workers=3) as pool:
    rows = [row for part in pool.map(fetch, values) for row in part]

cols = ["username", "caption", "like_count", "taken_at", "url", "code"]
with open("out.csv", "w", newline="") as f:
    w = csv.DictWriter(f, fieldnames=cols, extrasaction="ignore")
    w.writeheader()
    w.writerows(rows)

CSV export from the Threads User Posts Scraper API

out.csvcatalog sample · 1 row
username,caption,like_count,taken_at,url,code
zuck,500M monthly actives on Threads in less than 3 years.,17686,2026-06-16 10:59:56,https://www.threads.net/@zuck/post/DZpPDXbCeTt,DZpPDXbCeTt
Agents

AI Agent Access via MCP

MCP for the Threads User Posts Scraper API

The same endpoint is available to AI agents through the Scrapier MCP server at https://mcp.scrapier.io/mcp. One command registers it in Claude Code: claude mcp add -t http scrapier https://mcp.scrapier.io/mcp --header "X-API-Key: YOUR_API_KEY". The agent finds the endpoint with search_endpoints and calls it with run_scrape and the endpoint id threads-user-posts. It takes the same usernames input and costs the same 1 credit per page of posts. Setup for every client is on the Threads User Posts Scraper MCP page.

Integrations

Integration Paths by Role

No-code

n8n and Make

  1. Add an HTTP Request step
  2. GET the endpoint with your X-API-Key header
  3. Map the data.posts fields to your columns
Developers

Loop and paginate

for value in values: rows += get(value) while cur := page["data"]["next_cursor"]: page = get(cursor=cur)
AI agents

MCP tool in your agent

Call run_scrape with endpoint threads-user-posts from Claude, Cursor or Windsurf. Setup is on the MCP page.

Analysts

CSV and flattened JSON

Flatten each row into one CSV line, one column per field, ready for Sheets, Excel or a BI tool.

FAQ

Frequently Asked Questions

Is there a Threads page of posts API?

Yes. Scrapier's Threads User Posts Scraper API returns any public page of posts as JSON with one GET request and an X-API-Key header. No Threads app or login.

How do I call it from Python?

Use <code>requests.get</code> on <code>https://proxy.scrapier.io/api/v2/threads-user-posts/</code> with <code>params={'usernames': 'zuck'}</code> and <code>headers={"X-API-Key": KEY}</code>. Read <code>r.json()["data"]["posts"]</code>.

What happens when a call fails?

Any non-200 response is free. Retry 429 and 5xx with backoff; the API already retries upstream failures.

How much does it cost?

1 credit per successful call — about $1.58 per 1,000 pages of posts on the Pro plan. Failed calls are free.

Is there an OpenAPI spec?

Yes. It needs no key and covers every Scrapier endpoint.

Fetch public Threads pages of posts as typed JSON in one request

1 credit per page of posts · failed calls free