Threads Search Scraper
Threads posts matching a keyword, hashtag or phrase as typed JSON: caption, author, like, reply and repost counts and post time, sorted top or recent. 1 credit per call. No Threads login needed.
Free API key · 1 credit per page of search results · failed calls free
// GET /api/v2/threads-search/?queries=AI · sample from the catalog { "success": true, "data": { "query": "AI", "page": 1, "page_size": 18, "posts": [ { "postId": "3921506418558274796", "postUrl": "https://www.threads.com/@theeconomist/post/DLabcXYZ", "username": "theeconomist", "isVerified": true, "captionText": "Today the cost of providing AI services is subsidised by the labs...", "likeCount": 1240, "directReplyCount": 87, "repostCount": 34, "takenAt": 1718628028, "takenAtISO": "2026-06-17T12:40:28.000Z", "nextCursor": "GDA6...opaque-end-cursor", "keyword": "AI", "scraped_at": "2026-06-18T12:00:00.000Z" } ], "next_cursor": "eyJxIjoiQUkiLCJyIjowLCJhIjoiR0RBNi4uLiIsImxrIjp7fSwicCI6MX0" } }
| field | value | type | Has a value✓ |
|---|
Scrapier's Threads Search Scraper returns posts matching a keyword as JSON: captionText, username, likeCount, directReplyCount, repostCount, postUrl and takenAtISO, 18 posts per page in the catalog sample. It costs 1 credit per successful call. No Threads login.
Threads Search Scraper searches Threads posts for a keyword, hashtag or phrase and returns the matches as structured JSON. Each post carries its caption, author, verified flag, like, reply and repost counts, post time and URL, ready to pass directly to an LLM, index into a vector store or feed a social-listening pipeline. You can sort by top or recent and filter by author or date range. It is one of 6 Threads endpoints on the same API key used by 12,000+ developers. Next, look up the authors with the profile endpoint.
What data can I extract with Threads Search Scraper?
Using this Threads Search Scraper, you can extract the following data from public Threads pages of search results:
Want the exact field names? See the example output.
Try Threads Search 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 Search 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 Search Scraper to get public Threads pages of search results. Endpoint: GET https://proxy.scrapier.io/api/v2/threads-search/?queries={queries} with header "X-API-Key: YOUR_API_KEY" and a 210-second timeout. Send one value per call in queries; for a list, make one call per value, at most 3 in parallel. It returns JSON under data.posts: postId, postUrl, username, isVerified, captionText, likeCount, directReplyCount, repostCount, takenAt, takenAtISO, nextCursor, keyword. 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-search" (find it with search_endpoints).Use this scraper from ChatGPT, Claude or Cursor. Point your assistant at Scrapier and it reads Threads pages of search results 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 Search Scraper in the catalogIt lives under Scrapers / Threads.
- Enter a search termPut a keyword, hashtag or phrase such as
AIinqueries. Optionally setsortto top or recent,fromto one username, andbeforeorafteras YYYY-MM-DD dates. - 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 search results
queries takes one value per call, so for a list of keywords you loop: one request per keyword, and pass back data.next_cursor to read more results for the same keyword. 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 Search Scraper turns Threads search into clean rows. It suits social listening, trend research, brand monitoring and any workflow that needs the posts, authors and engagement behind a keyword without managing Threads sessions or developer credentials.
- Keyword
queriestakes a term, hashtag or phrase - Sorting
sortset to top or recent - Filters
from,beforeandafter - Engagement
likeCount,directReplyCount,repostCount - Author
usernameandisVerified - Paging
next_cursorreads more results
Proxies, retries and parsing run on Scrapier's side, so you send one request and get JSON back, at 1 credit per page of search results and 0 credits for a failed call.
Use cases
- Social listener searches a brand name each day with
sortset to recent, readscaptionTextandlikeCount, and flags posts that gain reach. - Trend analyst searches a hashtag set to top and saves
captionText,repostCountandtakenAtISOto chart a topic over time. - PR team searches a campaign phrase with
afterset to the launch date and collects everypostUrlin a report. - Researcher uses
fromwith a keyword to pull one author's posts on a topic for a discourse study. - AI engineer gives an agent a tool that searches Threads for a topic, then has an LLM summarise what people say.
Running these from an agent? Use the MCP integration and let Claude or Cursor call the scraper directly.
Why choose this Scraper API?
sort, from, before and after narrow results without post-processing your side.
directReplyCount and repostCount sit next to likeCount, so you can rank by reach.
The same key and response envelope cover search, user posts and profiles, so one call feeds the next without new code.
Input
The scraper takes one value per call in queries: a Threads search term, hashtag or phrase. It is required on the first call. Optional sort (top or recent), from (one username) and before / after (YYYY-MM-DD) are locked into the cursor. Send parameters in the query string (GET) or as a JSON body (POST).
| Name | Type | Required | Default | Description |
|---|---|---|---|---|
queries | string | Yes | — | A Threads search term, hashtag or phrase. One per call. Required on the first call. Aliases: search_query, searchQuery, keyword, q |
cursor | string | No | — | Pass back data.next_cursor from the previous response to get the next page; null means the last page |
sort | string | No | top | top or recent (default top). Locked in the cursor |
from | string | No | — | Only keep posts from this username (client-side filter). Locked in the cursor. Alias: from_user |
before | string | No | — | Only keep posts before this date, as YYYY-MM-DD. Locked in the cursor |
after | string | No | — | Only keep posts after this date, as YYYY-MM-DD. Locked in the cursor |
session_id | string | No | — | Optional Threads sessionid cookie, read fresh on every call. Anonymous calls still work but are capped at one 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 search ten keywords, make ten calls and page each with cursor. Booleans are the strings true or false.
Example input
{
"queries": "AI",
"sort": "top",
"from": "",
"before": "",
"after": "",
"session_id": "YOUR_SESSIONID",
"use_proxy": "true",
"raw_data": "false"
}Error codes
| Status | Meaning | Billed | Fix |
|---|---|---|---|
| 200 | Page of search results data returned in data.posts | Yes | — |
| 400 | Bad or missing input | No | Check queries: 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 13 fields, inside the standard data envelope. data also carries the query, 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": {
"query": "AI",
"page": 1,
"page_size": 18,
"posts": [
{
"postId": "3921506418558274796",
"postUrl": "https://www.threads.com/@theeconomist/post/DLabcXYZ",
"username": "theeconomist",
"isVerified": true,
"captionText": "Today the cost of providing AI services is subsidised by the labs...",
"likeCount": 1240,
"directReplyCount": 87,
"repostCount": 34,
"takenAt": 1718628028,
"takenAtISO": "2026-06-17T12:40:28.000Z",
"nextCursor": "GDA6...opaque-end-cursor",
"keyword": "AI",
"scraped_at": "2026-06-18T12:00:00.000Z"
}
],
"next_cursor": "eyJxIjoiQUkiLCJyIjowLCJhIjoiR0RBNi4uLiIsImxrIjp7fSwicCI6MX0"
}
}The catalog's sample response for queries=AI, labelled as a sample: live calls return the account's current values.
Post
| Field | Type | Example | Description |
|---|---|---|---|
posts.postId | string | "3921506418558274796" | Post ID |
posts.postUrl | string | "https://www.threads.com/@theeconomist/post/…" | URL of the post |
posts.captionText | string | "Today the cost of providing AI services is …" | Text of the post |
posts.takenAt | integer | 1718628028 | Post time as a Unix timestamp |
posts.takenAtISO | string | "2026-06-17T12:40:28.000Z" | Post time (ISO 8601) |
Engagement
| Field | Type | Example | Description |
|---|---|---|---|
posts.likeCount | integer | 1240 | Number of likes |
posts.directReplyCount | integer | 87 | Number of direct replies |
posts.repostCount | integer | 34 | Number of reposts |
Author
| Field | Type | Example | Description |
|---|---|---|---|
posts.username | string | "theeconomist" | Handle of the author |
posts.isVerified | boolean | true | Whether the author is verified |
Search context
| Field | Type | Example | Description |
|---|---|---|---|
posts.keyword | string | "AI" | The search term that matched this post |
posts.nextCursor | string | "GDA6...opaque-end-cursor" | Cursor recorded on the post row |
posts.scraped_at | string | "2026-06-18T12: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.query | string | "AI" | The search term you sent |
data.page | integer | 1 | Page number of this response |
data.page_size | integer | 18 | Number of posts on this page |
data.next_cursor | string | "eyJxIjoiQUkiLCJyIjowLCJhIjoiR0RBNi4uLiIsImx…" | 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 Search 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-search: 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-search/ 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-search with search_endpoints itself.
Pricing and Rate Limits
One Threads page of search results costs 1 credit, so 1,000 pages of search results 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 search results included | Per 1,000 pages of search results |
|---|---|---|---|---|
| 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-search/, 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 Search Scraper vs the Official Threads API
| Feature | Scrapier page of search results scraper | Official Threads API |
|---|---|---|
| Access needed | One Scrapier API key | A Meta developer app, access tokens and the permissions Meta grants |
| Which data | Posts by keyword, hashtag or phrase, sorted top or recent | Depends on the endpoints and permissions available to your app |
| Fields returned | 13 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 Search Scraper return?
Each post has postId, postUrl, captionText, username, isVerified, likeCount, directReplyCount, repostCount, takenAt, takenAtISO, keyword and scraped_at: 13 fields in data.posts. Each successful call costs 1 credit and needs no Threads login.
What can I search for?
One keyword, hashtag or phrase per call in queries, for example AI. Aliases search_query, searchQuery, keyword and q work too. To search several terms, make one call per term.
Can I sort by top or recent posts?
Yes. Set sort to top or recent; the default is top. The sort is locked into the cursor, so keep it the same while you page through one search with data.next_cursor.
Can I filter by author or date?
Yes. from keeps only posts from one username, and before and after keep posts on one side of a YYYY-MM-DD date. The filters apply on Scrapier's side to the results and are locked into the cursor.
Does Threads Search Scraper need a Threads login?
Not required. Anonymous calls work but are capped at one page. You can add your own Threads sessionid cookie in session_id, read fresh on every call, which is meant for paging beyond that. Never share a cookie you do not own.
How many posts come back per page?
The catalog sample shows page_size 18. Pass data.next_cursor back as cursor to read more; null means the end. Each page is one call and costs 1 credit, and anonymous calls are capped at one page.
Does Threads Search 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-search 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 Search 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 Search 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 Search Scraper with Python?
Send a GET request with the requests library to https://proxy.scrapier.io/api/v2/threads-search/ with params={"queries": "AI", "sort": "recent"}, 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 Search Results
Public Threads pages of search results as JSON, 1 credit each, from REST or MCP.