Threads User Posts Scraper API
Last updated: · REST · JSON
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
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.
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)
// Replace YOUR_API_KEY with the key from your Scrapier dashboardconst API_KEY = "YOUR_API_KEY";const params = new URLSearchParams({ usernames: "zuck",});const res = await fetch(`https://proxy.scrapier.io/api/v2/threads-user-posts/?${params}`, { headers: { "X-API-Key": API_KEY }, signal: AbortSignal.timeout(210_000),});if (!res.ok) throw new Error(`HTTP ${res.status}`);const { data } = await res.json();console.log(data.posts);
# One GET request. The key goes in a header, never in the URL.GET /api/v2/threads-user-posts/?usernames=zuck HTTP/1.1Host: proxy.scrapier.ioX-API-Key: YOUR_API_KEYAccept: application/json
# Scrapier publishes an OpenAPI spec that covers every endpoint. No API key needed.curl -O https://proxy.scrapier.io/api/v2/openapi.json# Import openapi.json into Postman, Insomnia, Bruno or a code generator,# then add your key as the X-API-Key header.
# 1. Add the Scrapier MCP server to Claude Codeclaude mcp add -t http scrapier https://mcp.scrapier.io/mcp --header "X-API-Key: YOUR_API_KEY"# 2. Ask your agent. It finds the endpoint with search_endpoints# and calls it with run_scrape:"Get the latest Threads posts from the account zuck"run_scrape("threads-user-posts", {usernames: "zuck"})
Threads User Posts Scraper API in Python
Plain requests is all you need — no SDK. Every response is typed JSON.
Install
Threads User Posts Scraper API in JavaScript
Works in Node 18+, Deno, Bun and edge runtimes with the built-in fetch.
Check your setup
Threads User Posts Scraper API over HTTP
One GET request. Auth is a single X-API-Key header.
Check your setup
Threads User Posts Scraper API OpenAPI definition
Download the spec once, then import it into the tools you already use. No key is needed to fetch it.
Download the spec
Threads User Posts Scraper API over MCP
The same endpoint is a tool call for Claude Code, Cursor and Windsurf. Same usernames, same 1 credit per page of posts.
Install
Other ways to call it
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.
GET /api/v2/threads-user-posts/?usernames=zuckPress Run request to send it. Without a key you get the catalog sample.
Failed calls are not billed.
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 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
Response Schema Reference
Every field in the sample response. Field names stay the same on every call.
| Field | Type | Example | Description |
|---|---|---|---|
posts.id | string | "3920731152608519405_63055343223" | Post ID |
posts.code | string | "DZpPDXbCeTt" | Short post code used in the URL |
posts.url | string | "https://www.threads.net/@zuck/post/DZpPDXbC…" | URL of the post |
posts.caption | string | "500M monthly actives on Threads in less tha…" | Text of the post |
posts.taken_at | string | "2026-06-16 10:59:56" | When the post was published |
posts.like_count | integer | 17686 | Number of likes |
posts.username | string | "zuck" | Handle of the author |
posts.input_username | string | "zuck" | The usernames value you sent |
posts.scraped_at | string | "2026-06-20T12:00:00.000Z" | When Scrapier read the post (ISO 8601) |
success | boolean | true | true on every 200 response |
data.username | string | "zuck" | The account you asked for |
data.page | integer | 1 | Page number of this response |
data.page_size | integer | 25 | Number of posts on this page |
data.next_cursor | string | "eyJ1IjoienVjayIsImEiOiJBQUFceDNkIiwicCI6Mn0" | Pass back as cursor for the next page; null on the last page |
Request Parameters Reference
| Name | Type | Required | Default | Description | Example |
|---|---|---|---|---|---|
usernames | string | Yes | — | A Threads username. One per call. Required on the first call, ignored when cursor is set. Aliases: username, user, query, q | zuck |
cursor | string | No | — | Pass back data.next_cursor from the previous response to get the next page; null means the last page | — |
use_proxy | boolean | No | true | Use Scrapier's residential proxy pool when true (default true). Leave as is | true |
raw_data | boolean | No | false | Return the raw upstream payload under raw_responses instead of the formatted posts | true |
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 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.
Speed, Cost and Concurrency
| Metric | Value | Source |
|---|---|---|
| Cost of a successful call | 1 credit | Scrapier catalog |
| Cost of a failed call | 0 credits | Any non-2xx response |
| Parallel requests per key | 3 | Above that: 429 with Retry-After |
| Recommended client timeout | 210 seconds | Scrapier 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 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
429withRetry-After. - Large results come in pages; pass
data.next_cursorback ascursor. - Fields Threads does not show are not returned.
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.
| Feature | Scrapier page of posts scraper | Official Threads API |
|---|---|---|
| Access needed | One Scrapier API key | A Meta developer app, access tokens and the permissions Meta grants |
| Which data | An account's posts, a page at a time | Depends on the endpoints and permissions available to your app |
| Fields returned | 9 fields, as in the catalog sample | Depends on the fields you request |
| Rate limits | Up to 3 parallel requests per key; 429 with Retry-After | Limits set by Meta per app |
| Setup | Sign up, copy a key, send a request | Create an app, set up OAuth, manage tokens |
| Cost | 1 credit per call, from $1.20 per 1,000 calls | Set by Meta's terms |
Errors and Retry Handling
| Status | Meaning | Billed | Fix |
|---|---|---|---|
| 200 | Page of posts data returned in data.posts | Yes | — |
| 400 | Bad or missing input | No | Check usernames: one value per call |
| 401 | X-API-Key header missing | No | Add the header |
| 402 | Out of credits (body has balance) | No | Top up; retrying will not help |
| 403 | Invalid or revoked API key | No | Check the key in your dashboard |
| 429 | Throttled | No | Wait Retry-After seconds, then retry |
| 5xx | Upstream failure or timeout | No | Retry 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
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 and Rate Limits
| Plan | Monthly price | Pages Of Posts included | Cost per 1,000 |
|---|---|---|---|
| Hobby | $29 | 15,000 | $1.93 |
| Pro | $79 | 50,000 | $1.58 |
| Scale | $299 | 250,000 | $1.20 |
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 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.
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
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
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.
Integration Paths by Role
n8n and Make
- Add an HTTP Request step
- GET the endpoint with your
X-API-Keyheader - Map the
data.postsfields to your columns
Loop and paginate
MCP tool in your agent
Call run_scrape with endpoint threads-user-posts from Claude, Cursor or Windsurf. Setup is on the MCP page.
CSV and flattened JSON
Flatten each row into one CSV line, one column per field, ready for Sheets, Excel or a BI tool.
Legal and Compliance Notes
Scraping publicly available Threads data is generally lawful in many countries, but the answer depends on what you collect, where you are and how you use it. In the US, hiQ Labs v. LinkedIn is the case most often cited on public-data scraping. Scrapier returns only public data any visitor can see without logging in. Under GDPR and similar laws, collecting public data can be permissible, but how you store and use personal data, such as names, handles or posts, must still comply with local data-protection rules, and Threads' terms apply. Consult legal counsel if your use case involves bulk storage of personal data. This is not legal advice; see our Terms of Use.
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