Threads Profile Info Scraper
Any public Threads account as one typed JSON record: username, full name, bio, follower count, verified and private flags, bio links and profile picture. 1 credit per call. No Threads login, no proxies.
Free API key · 1 credit per profile · failed calls free
// GET /api/v2/threads-profile-info/?usernames=trendspider · sample from the catalog { "success": true, "data": { "usernames": "trendspider", "result": { "input_username": "trendspider", "success": true, "profile_pic_url": "https://instagram.fdac8-1.fna.fbcdn.net/v/t51.2885-19/324065807_885673889454586_5057027684557636343_n.jpg?stp=dst-jpg_s150x150_tt6&...", "friendship_status": null, "has_onboarded_to_text_post_app": true, "pk": "63069450921", "text_post_app_is_private": false, "username": "trendspider", "text_post_app_remove_mention_entrypoint": null, "text_app_custom_feeds": null, "gating": null, "platform_newsletter_info": null, "platform_podcast_info": null }, "next_cursor": null } }
| field | value | type | Has a value✓ |
|---|
Scrapier's Threads Profile Info Scraper returns one public account as JSON: username, full_name, biography, follower_count, is_verified, text_post_app_is_private, bio_links and profile_pic_url. It costs 1 credit per successful call. No Threads login.
Threads Profile Info Scraper looks up one Threads account and returns a single record: who it is, how big it is and what it links to. Give it a username, an @handle, a profile or post URL, or an id:<numeric user id>, and you get the bio, follower count, verified and private flags, bio links and profile picture in structured JSON, ready to pass directly to an LLM, join to a CRM or store for later. It is one of 6 Threads endpoints on the same API key used by 12,000+ developers. Next, chain it with user posts or search.
What data can I extract with Threads Profile Info Scraper?
Using this Threads Profile Info Scraper, you can extract the following data from public Threads profiles:
Want the exact field names? See the example output.
Try Threads Profile Info 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 Profile Info 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 Profile Info Scraper to get public Threads profiles. Endpoint: GET https://proxy.scrapier.io/api/v2/threads-profile-info/?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.result: input_username, success, profile_pic_url, friendship_status, has_onboarded_to_text_post_app, pk, text_post_app_is_private, username, text_post_app_remove_mention_entrypoint, text_app_custom_feeds, gating, platform_newsletter_info. 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-profile-info" (find it with search_endpoints).Use this scraper from ChatGPT, Claude or Cursor. Point your assistant at Scrapier and it reads Threads profiles 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 Profile Info Scraper in the catalogIt lives under Scrapers / Threads.
- Enter an accountPut a username such as
trendspiderinusernames. An @handle, a profile or post URL, orid:followed by the numeric user ID also works. - 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 resultsThe call returns one record in
result: store it as is, or flatten it to a CSV row.next_cursoris always null for this endpoint.
How to scale to bulk Threads profiles
usernames takes one value per call, so for a list of accounts you loop: one request per account. There is nothing to page, because this endpoint returns a single record and next_cursor is always null. 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 Profile Info Scraper turns an account into one clean row. It suits lead lists, creator research, brand monitoring and any workflow that needs bio, reach and links for a Threads account without managing Threads sessions or developer credentials.
- Identity
username,full_nameand numericpk - Bio
biographyplustext_app_biographyfragments - Reach
follower_countfor the account - Flags
is_verifiedandtext_post_app_is_private - Links
bio_linkswith url and link id - Pictures
profile_pic_urlandhd_profile_pic_versions
Proxies, retries and parsing run on Scrapier's side, so you send one request and get JSON back, at 1 credit per profile and 0 credits for a failed call.
Use cases
- Sales researcher looks up a list of Threads handles, reads
follower_count,biographyandbio_links, and adds the site link to a lead sheet. - Creator marketer checks
follower_countandis_verifiedfor a shortlist of creators before outreach. - Brand monitor pulls competitor accounts each week and records
follower_countto chart growth. - Analyst stores
biographyandfull_namefor a set of accounts to group them by topic. - AI engineer gives an agent a tool that fetches a Threads profile, then has an LLM summarise who the account is.
Running these from an agent? Use the MCP integration and let Claude or Cursor call the scraper directly.
Why choose this Scraper API?
usernames accepts a username, @handle, profile or post URL or an id: numeric ID, so you can feed it whatever you already have.
bio_links and hd_profile_pic_versions come back in the same call, so you need no second request.
The same key and response envelope cover profiles, user 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, an @handle, a profile or post URL or id: plus the numeric user ID (user_id takes bare digits). It is required. Send parameters in the query string (GET) or as a JSON body (POST).
| Name | Type | Required | Default | Description |
|---|---|---|---|---|
usernames | string | Yes | — | A Threads username, @handle, profile or post URL, or id:<numeric user id> (user_id takes bare digits). One per call, required. Aliases: username, handles, handle, urls, url, profile_urls, profile_url, user_ids, user_id |
cursor | string | No | — | Not needed here: this endpoint returns a single record and next_cursor is always null |
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 record |
One value per call: to read ten accounts, make ten calls. Booleans are the strings true or false.
Example input
{
"usernames": "trendspider",
"use_proxy": "true",
"raw_data": "false"
}Error codes
| Status | Meaning | Billed | Fix |
|---|---|---|---|
| 200 | Profile data returned in data.result | 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 single record under result with 28 fields, inside the standard data envelope. data also carries your usernames input and next_cursor, which is always null here. 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": {
"usernames": "trendspider",
"result": {
"input_username": "trendspider",
"success": true,
"profile_pic_url": "https://instagram.fdac8-1.fna.fbcdn.net/v/t51.2885-19/324065807_885673889454586_5057027684557636343_n.jpg?stp=dst-jpg_s150x150_tt6&...",
"friendship_status": null,
"has_onboarded_to_text_post_app": true,
"pk": "63069450921",
"text_post_app_is_private": false,
"username": "trendspider",
"text_post_app_remove_mention_entrypoint": null,
"text_app_custom_feeds": null,
"gating": null,
"platform_newsletter_info": null,
"platform_podcast_info": null,
"platform_podcast_episode_info": null,
"follower_count": 68011,
"profile_context_facepile_users": null,
"text_post_app_public_views": null,
"hd_profile_pic_versions": [
{
"height": 320,
"url": "https://instagram.fdac8-1.fna.fbcdn.net/v/t51.2885-19/324065807_885673889454586_5057027684557636343_n.jpg?stp=dst-jpg_s320x320_tt6&...",
"width": 320
},
{
"height": 640,
"url": "https://instagram.fdac8-1.fna.fbcdn.net/v/t51.2885-19/324065807_885673889454586_5057027684557636343_n.jpg?stp=dst-jpg_s640x640_tt6&...",
"width": 640
}
],
"is_verified": true,
"biography": "Award-Winning 🏆 All-in-One Trading Platform.\nCharts, scans, backtests, alerts, AI tools, data & more.",
"text_app_biography": {
"text_fragments": {
"fragments": [
{
"fragment_type": "plaintext",
"link_fragment": null,
"mention_fragment": null,
"plaintext": "Award-Winning 🏆 All-in-One Trading Platform.\nCharts, scans, backtests, alerts, AI tools, data & more.",
"inline_sticker_fragment": null,
"linkified_web_url": null,
"linkified_in_app_url": null,
"styling_info": null
}
]
}
},
"full_name": "TrendSpider",
"bio_links": [
{
"url": "http://trendspider.com/",
"lynx_url": "https://l.threads.com/?u=http%3A%2F%2Ftrendspider.com%2F&e=...",
"link_id": "18254716222286461",
"title": "",
"is_verified": false
}
],
"profile_tags": {
"edges": []
},
"transparency_label": null,
"show_text_post_app_badge": true,
"id": "63069450921",
"scraped_at": "2026-10-04T10:12:41.512Z"
},
"next_cursor": null
}
}The catalog's sample response for usernames=trendspider, labelled as a sample: live calls return the account's current values.
Identity
| Field | Type | Example | Description |
|---|---|---|---|
result.username | string | "trendspider" | Threads handle |
result.full_name | string | "TrendSpider" | Display name |
result.pk | string | "63069450921" | Numeric user ID |
result.id | string | "63069450921" | Numeric user ID (same as pk) |
result.input_username | string | "trendspider" | The username you sent |
result.success | boolean | true | Whether the lookup worked for this account |
Bio and links
| Field | Type | Example | Description |
|---|---|---|---|
result.biography | string | "Award-Winning 🏆 All-in-One Trading Platform…" | Bio text |
result.text_app_biography | object | {…} | Bio split into fragments (plaintext, links, mentions) |
result.bio_links | array | 1 items | Links in the bio (url, lynx_url, link_id, title, is_verified) |
result.profile_tags | object | {…} | Profile tags (edges), often empty |
Reach and flags
| Field | Type | Example | Description |
|---|---|---|---|
result.follower_count | integer | 68011 | Number of followers |
result.is_verified | boolean | true | Whether the account is verified |
result.text_post_app_is_private | boolean | false | Whether the account is private |
result.text_post_app_public_views | null | null | Public views figure, or null |
result.has_onboarded_to_text_post_app | boolean | true | Whether the user has joined Threads |
result.show_text_post_app_badge | boolean | true | Whether the Threads badge shows |
result.transparency_label | null | null | Transparency label, or null |
result.friendship_status | null | null | Relationship to the viewer, or null |
result.gating | null | null | Content gating info, or null |
result.profile_context_facepile_users | null | null | Facepile users, or null |
Pictures
| Field | Type | Example | Description |
|---|---|---|---|
result.profile_pic_url | string | "https://instagram.fdac8-1.fna.fbcdn.net/v/t…" | Profile picture URL |
result.hd_profile_pic_versions | array | 2 items | Larger picture versions (height, width, url) |
Other Threads data
| Field | Type | Example | Description |
|---|---|---|---|
result.text_post_app_remove_mention_entrypoint | null | null | Mention setting, or null |
result.text_app_custom_feeds | null | null | Custom feeds, or null |
result.platform_newsletter_info | null | null | Newsletter info, or null |
result.platform_podcast_info | null | null | Podcast info, or null |
result.platform_podcast_episode_info | null | null | Podcast episode info, or null |
Timing
| Field | Type | Example | Description |
|---|---|---|---|
result.scraped_at | string | "2026-10-04T10:12:41.512Z" | When Scrapier read the profile (ISO 8601) |
Response envelope
| Field | Type | Example | Description |
|---|---|---|---|
success | boolean | true | true on every 200 response |
data.usernames | string | "trendspider" | Your input, echoed back |
data.next_cursor | null | null | Always null: this endpoint returns a single record |
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 Profile Info 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-profile-info: 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-profile-info/ 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-profile-info with search_endpoints itself.
Pricing and Rate Limits
One Threads profile costs 1 credit, so 1,000 profiles 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 | Profiles included | Per 1,000 profiles |
|---|---|---|---|---|
| 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-profile-info/, 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 Profile Info Scraper vs the Official Threads API
| Feature | Scrapier profile scraper | Official Threads API |
|---|---|---|
| Access needed | One Scrapier API key | A Meta developer app, access tokens and the permissions Meta grants |
| Which data | Public profile by username, @handle, URL or numeric ID | Depends on the endpoints and permissions available to your app |
| Fields returned | 28 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 Profile Info Scraper return?
One record under data result with username, full_name, biography, follower_count, is_verified, text_post_app_is_private, bio_links, profile_pic_url, hd_profile_pic_versions and more: 28 fields. Each successful call costs 1 credit and needs no Threads login.
What can I send as input?
One value in usernames: a Threads username, an @handle, a profile or post URL, or id: followed by the numeric user ID. Aliases such as username, handle, url and user_id work too. Send one account per call and loop for a list.
Can I scrape a Threads profile without logging in?
Yes. No Threads account or cookie is used: you send your Scrapier API key in the X-API-Key header and the username, and get JSON back. Only public data is returned. A private account only exposes what any visitor can see.
Does the call return an account's follower count?
Yes. follower_count holds the number of followers at the time of the call, and scraped_at shows when Scrapier read it. Run the call on a schedule and store the values if you want to chart follower growth.
Does it return the links in the bio?
Yes. bio_links is a list with the url, a lynx_url wrapper, a link_id and a title for each link. For a company account the first url is usually its website, which is handy for lead lists.
Is there pagination?
No. This endpoint returns one record, and next_cursor is always null. To read the account's posts, use the Threads user posts endpoint, which pages with next_cursor.
Does Threads Profile Info 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-profile-info 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 Profile Info 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 Profile Info 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 Profile Info Scraper with Python?
Send a GET request with the requests library to https://proxy.scrapier.io/api/v2/threads-profile-info/ with params={"usernames": "trendspider"}, your key in the X-API-Key header and timeout=210. Read r.json()["data"]["result"]: 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 Profiles
Public Threads profiles as JSON, 1 credit each, from REST or MCP.