Threads User Posts Scraper
A public Threads account's posts as typed JSON, a page at a time: caption, like count, post time, post code and URL. 1 credit per call. No Threads login, no proxies, and a cursor to page on.
Free API key · 1 credit per page of posts · failed calls free
// GET /api/v2/threads-user-posts/?usernames=zuck · sample from the catalog { "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" } }
| field | value | type | Has a value✓ |
|---|
Scrapier's Threads User Posts Scraper returns a public account's posts as JSON: caption, like_count, taken_at, url, code and id, 25 posts per page in the catalog sample. It costs 1 credit per successful call. No Threads login.
Threads User Posts Scraper reads the posts of one public Threads account. Give it a username and it returns a page of posts, each with its caption, like count, post time, post code and URL, as structured JSON ready to pass directly to an LLM, index into a vector store or load into a spreadsheet. Pass the returned cursor back to read older posts. It is one of 6 Threads endpoints on the same API key used by 12,000+ developers. Next, join it with the profile endpoint.
What data can I extract with Threads User Posts Scraper?
Using this Threads User Posts Scraper, you can extract the following data from public Threads pages of posts:
Want the exact field names? See the example output.
Try Threads User Posts Scraper Live
Press Run to see the catalog sample. Add your API key and it runs a real call to the Scrapier API from your browser. The key is sent only to proxy.scrapier.io and never stored.
+ Run live with your API key
How to use Threads User Posts Scraper
Hand it to your AI assistant, or run it yourself in five steps.
Copy to your AI assistant
Paste this into ChatGPT, Claude or Cursor and it knows how to call the scraper.
Use the Scrapier Threads User Posts Scraper to get public Threads pages of posts. Endpoint: GET https://proxy.scrapier.io/api/v2/threads-user-posts/?usernames={usernames} with header "X-API-Key: YOUR_API_KEY" and a 210-second timeout. Send one value per call in usernames; for a list, make one call per value, at most 3 in parallel. It returns JSON under data.posts: username, id, code, caption, like_count, taken_at, url, input_username, scraped_at. Each successful call costs 1 credit; failed calls are free. If you support MCP, run: claude mcp add -t http scrapier https://mcp.scrapier.io/mcp --header "X-API-Key: YOUR_API_KEY" and call run_scrape with endpoint "threads-user-posts" (find it with search_endpoints).Use this scraper from ChatGPT, Claude or Cursor. Point your assistant at Scrapier and it reads Threads pages of posts on its own: no glue code, no scraping logic in your prompts.
Run it yourself
- Get your free Scrapier API keySign up at app.scrapier.io; the free tier lets you try it first.
- Open Threads User Posts Scraper in the catalogIt lives under Scrapers / Threads.
- Enter an accountPut a Threads username such as
zuckinusernames. It is required on the first call and ignored once you send acursor. - Send your API requestOne GET with your key in the
X-API-Keyheader, or onerun_scrapecall from your agent. Set a 210-second client timeout. - Save your resultsEach call returns a page of posts in
data.posts: store it as is, or flatten it to CSV. Passdata.next_cursorback ascursorfor the next page until it is null.
How to scale to bulk Threads pages of posts
usernames takes one value per call, so for a list of accounts you loop: one request per account, and pass back data.next_cursor to page through older posts. Run up to 3 requests in parallel per API key; above that the API answers 429 with a Retry-After header, and throttled calls cost nothing. Each call is 1 credit and failed calls are free, so 1,000 calls cost 1,000 credits, inside the Hobby plan's 15,000.
Features
Threads User Posts Scraper turns an account's feed into clean rows. It suits brand and competitor monitoring, creator research, content analysis and any workflow that needs the captions and like counts of Threads posts without managing sessions or developer credentials.
- Caption
captionholds the text of the post - Likes
like_countfor each post - Timing
taken_atshows when it was posted - Links
urlandcodepoint to the post - Author
usernameof the account - Paging
next_cursorwalks the account page by page
Proxies, retries and parsing run on Scrapier's side, so you send one request and get JSON back, at 1 credit per page of posts and 0 credits for a failed call.
Use cases
- Brand monitor checks a list of competitor Threads accounts each morning, reads
captionandlike_countof the latest posts and sends the top ones to a team channel. - Content strategist pulls an account's posts and sorts them by
like_countto see which topics land. - Researcher stores
caption,taken_atandlike_countfor a set of accounts as a dataset for a discourse study. - Social team archives the
urlandcaptionof every post from a partner account for a weekly report. - AI engineer gives an agent a tool that fetches an account's recent posts, then summarises the themes with an LLM.
Running these from an agent? Use the MCP integration and let Claude or Cursor call the scraper directly.
Why choose this Scraper API?
data.next_cursor lets you walk back through an account's posts one call at a time, until it returns null.
Each post carries its url and code, so you can open, cite or dedupe it without a second call.
The same key and response envelope cover profiles, posts and search, so one call feeds the next without new code.
Input
The scraper takes one value per call in usernames: a Threads username. It is required on the first call and ignored once you send a cursor. Send parameters in the query string (GET) or as a JSON body (POST).
| Name | Type | Required | Default | Description |
|---|---|---|---|---|
usernames | string | Yes | — | A Threads username. One per call. Required on the first call, ignored when cursor is set. Aliases: username, user, query, q |
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 |
raw_data | boolean | No | false | Return the raw upstream payload under raw_responses instead of the formatted posts |
One value per call: to read ten accounts, make ten calls and page each with cursor. Booleans are the strings true or false.
Example input
{
"usernames": "zuck",
"use_proxy": "true",
"raw_data": "false"
}Error codes
| 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.
Output
Typed JSON with the same schema on every call. One call returns a page of posts under posts, each with 9 fields, inside the standard data envelope. data also carries the username, page, page_size and next_cursor. Field names stay the same on every call. Set raw_data to true if you want the raw payload instead.
Example output
{
"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"
}
}The catalog's sample response for usernames=zuck, labelled as a sample: live calls return the account's current values.
Post
| 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 |
Engagement
| Field | Type | Example | Description |
|---|---|---|---|
posts.like_count | integer | 17686 | Number of likes |
Author and input
| Field | Type | Example | Description |
|---|---|---|---|
posts.username | string | "zuck" | Handle of the author |
posts.input_username | string | "zuck" | The usernames value you sent |
Timing
| Field | Type | Example | Description |
|---|---|---|---|
posts.scraped_at | string | "2026-06-20T12:00:00.000Z" | When Scrapier read the post (ISO 8601) |
Response envelope and paging
| Field | Type | Example | Description |
|---|---|---|---|
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 |
How does it work?
Scrapier sends each request through its residential proxy pool (use_proxy, on by default), so you never manage IPs or proxy accounts.
Retries and parsing of Threads responses happen on Scrapier's side. You send one HTTP request and get typed JSON back.
Only publicly visible data is returned: what any visitor sees without signing in. No Threads account is needed unless this page says otherwise.
The schema is stable. When Threads changes, Scrapier updates the scraper and the field names stay the same.
How do you integrate Threads User Posts Scraper into your stack?
It works with what you already use: any HTTP client, AI agents over MCP, and no-code automation tools. Code samples for cURL, Python and Node.js are on the API tab.
MCP integration for AI agents
This registers the Scrapier MCP server, whose tools reach every Scrapier scraper, including threads-user-posts: the agent finds it with search_endpoints and calls it with run_scrape. Works with Claude Code, Cursor and Windsurf. MCP calls are billed like REST: 1 credit per successful call. Full MCP setup →
No-code tools (n8n, Make, LangChain)
Use the HTTP Request node with your Scrapier API key in an X-API-Key header and point it at /api/v2/threads-user-posts/ with the input as a query parameter. Map data into the next node.
Add an HTTP "Make a request" module with the same header and URL, and parse the response as JSON. Map the fields you need straight into Sheets, Airtable or your CRM.
Wrap the endpoint in a requests-based tool, or load the Scrapier MCP server through LangChain's MCP adapters so the agent finds threads-user-posts with search_endpoints itself.
Pricing and Rate Limits
One Threads page of posts costs 1 credit, so 1,000 pages of posts cost 1,000 credits: $1.58 on the Pro plan. Failed and empty calls are not billed. Run up to 3 requests in parallel per key; above that the API answers 429 with a Retry-After header.
| Plan | Monthly price | Credits | Pages of posts included | Per 1,000 pages of posts |
|---|---|---|---|---|
| Hobby | $29 | 15,000 | 15,000 | $1.93 |
| Pro | $79 | 50,000 | 50,000 | $1.58 |
| Scale | $299 | 250,000 | 250,000 | $1.20 |
| Enterprise | Custom volume and terms | |||
Prices from the live billing page. See all plans and limits.
Call cost and timing
How we measure this
Credit cost, pagination and the sample come from the live catalog (GET /api/v2/endpoints, /threads-user-posts/, checked 9 Nov 2026). Concurrency and timeout guidance come from the rate limits page of the docs. Scrapier does not publish latency or success-rate figures for this endpoint, so none are shown here.
Threads User Posts Scraper vs the Official Threads API
| 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 |
The official Threads API is the better choice when you publish posts, manage replies or act on behalf of an account you own.
Is it legal to scrape Threads data?
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
What fields does Threads User Posts Scraper return?
Each post has id, code, url, caption, taken_at, like_count, username, input_username and scraped_at: 9 fields in data.posts. Each successful call costs 1 credit and needs no Threads login.
How many posts come back per call?
The catalog sample shows page_size 25 for a page of posts. To get more, pass data.next_cursor back as cursor; null means you reached the end. Each page is one call and costs 1 credit.
Can I scrape all the posts of a Threads profile?
You can page through them. Call once with usernames, then pass data.next_cursor back as cursor on each following call until it is null. Each page costs 1 credit, so the total depends on how many pages the account has.
Does it return replies or only the account's own posts?
The fields in the catalog sample describe posts of the account: caption, like_count, taken_at and url. Replies under a post are a separate Threads endpoint, not covered by this page, so this page makes no claim about them.
Does it return reply or repost counts?
No. The catalog sample for this endpoint has caption, like_count, taken_at, url, code, id and the input fields only. For reply and repost counts per post, the Threads post search endpoint returns directReplyCount and repostCount.
What input does it need?
One Threads username in usernames, for example zuck. Aliases username, user, query and q work too. It is required on the first call and ignored when you pass a cursor. Send one account per call and loop for a list.
Does Threads User Posts Scraper work with Claude, ChatGPT and other AI agent tools?
Yes. Connect the Scrapier MCP server with claude mcp add -t http scrapier https://mcp.scrapier.io/mcp and your API key in an X-API-Key header; it works in Claude Code, Cursor and Windsurf. The agent finds threads-user-posts with search_endpoints and calls it with run_scrape. Any agent that can call an HTTP endpoint can use the REST API directly.
How fast does Threads User Posts Scraper run?
Scrapier does not publish a latency figure for this endpoint. Each call reads Threads live. Set a client timeout of 210 seconds, as the docs recommend for every endpoint, and retry a failed call, which costs nothing.
What happens if the input is wrong or Threads returns nothing?
If a call fails, the API returns a non-2xx status and costs 0 credits. In code, check the status, then skip that input or retry it later. Throttled calls (429 with a Retry-After header) are free as well, so retry loops cost nothing.
How does it compare to other Threads scrapers?
Scrapier charges a flat 1 credit per successful call, and failed calls are free; platforms that bill compute units vary with run time and infrastructure. The same API key and MCP server reach all 199 Scrapier endpoints. Scrapier returns structured JSON for public Threads data.
Does it return data in a format LLMs can use directly?
Yes. Every response is typed JSON with the same field names on every call: no HTML parsing and no selectors. Pass it straight to an LLM, index it into a vector store or return it from an agent tool.
How much does it cost to run Threads User Posts Scraper 1,000 times?
1,000 credits, because each call is 1 credit. That is about $1.93 on Hobby, $1.58 on Pro and $1.20 on Scale, at the plans' price per credit. Failed calls are free.
How do I use Threads User Posts Scraper with Python?
Send a GET request with the requests library to https://proxy.scrapier.io/api/v2/threads-user-posts/ with params={"usernames": "zuck"}, your key in the X-API-Key header and timeout=210. Read r.json()["data"]["posts"]: it is already JSON, so no HTML parsing is needed.
Is it legal to scrape Threads data?
It depends on your use and your country, so this is not legal advice. Scrapier returns public Threads data only. Threads' terms and privacy law such as GDPR or CCPA apply to how you store and use it. Collect only what you need, and ask a lawyer about your specific case.
Your feedback
Found a bug or missing a field? Let us know. Write to support@scrapier.io and the team replies to every report.
Start Scraping Threads Pages Of Posts
Public Threads pages of posts as JSON, 1 credit each, from REST or MCP.