Threads Profile Info Scraper API
Last updated: · REST · JSON
Send GET https://proxy.scrapier.io/api/v2/threads-profile-info/?usernames=trendspider with your key in the X-API-Key header. You get the profile back as JSON. 1 credit per profile; failed calls are free.
- 1 credit per profile
- Failed calls free
- 3 parallel requests per key
Call the Threads Profile Info Scraper API
Use the Threads Profile Info 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": "trendspider",}r = requests.get( "https://proxy.scrapier.io/api/v2/threads-profile-info/", headers={"X-API-Key": API_KEY}, params=params, timeout=210,)r.raise_for_status()# The result sits under data.resultresult = r.json()["data"]["result"]print(result)
// Replace YOUR_API_KEY with the key from your Scrapier dashboardconst API_KEY = "YOUR_API_KEY";const params = new URLSearchParams({ usernames: "trendspider",});const res = await fetch(`https://proxy.scrapier.io/api/v2/threads-profile-info/?${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.result);
# One GET request. The key goes in a header, never in the URL.GET /api/v2/threads-profile-info/?usernames=trendspider 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 Threads profile for the account trendspider"run_scrape("threads-profile-info", {usernames: "trendspider"})
Threads Profile Info Scraper API in Python
Plain requests is all you need — no SDK. Every response is typed JSON.
Install
Threads Profile Info Scraper API in JavaScript
Works in Node 18+, Deno, Bun and edge runtimes with the built-in fetch.
Check your setup
Threads Profile Info Scraper API over HTTP
One GET request. Auth is a single X-API-Key header.
Check your setup
Threads Profile Info 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 Profile Info Scraper API over MCP
The same endpoint is a tool call for Claude Code, Cursor and Windsurf. Same usernames, same 1 credit per profile.
Install
Other ways to call it
Threads Profile Info 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-profile-info/?usernames=trendspiderPress 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": {
"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
}
}Data You Can Extract
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. Every field below comes from the catalog sample response, as typed JSON.
Identity
6 fields in the response.
- username
- full_name
- pk
- id
- input_username
- success
Bio and links
4 fields in the response.
- biography
- text_app_biography
- bio_links
- profile_tags
Reach and flags
10 fields in the response.
- follower_count
- is_verified
- text_post_app_is_private
- text_post_app_public_views
- has_onboarded_to_text_post_app
- show_text_post_app_badge
- transparency_label
- friendship_status
- +2 more
Pictures
2 fields in the response.
- profile_pic_url
- hd_profile_pic_versions
Other Threads data
5 fields in the response.
- text_post_app_remove_mention_entrypoint
- text_app_custom_feeds
- platform_newsletter_info
- platform_podcast_info
- platform_podcast_episode_info
Timing
1 field in the response.
- scraped_at
Response envelope
3 fields in the response.
- success
- data.usernames
- data.next_cursor
Response Schema Reference
Every field in the sample response. Field names stay the same on every call.
| 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 |
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 |
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 |
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) |
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 |
result.scraped_at | string | "2026-10-04T10:12:41.512Z" | When Scrapier read the profile (ISO 8601) |
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 |
Request Parameters Reference
| Name | Type | Required | Default | Description | Example |
|---|---|---|---|---|---|
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 | trendspider |
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 | true |
raw_data | boolean | No | false | Return the raw upstream payload under raw_responses instead of the formatted record | true |
One value per call: to read ten accounts, make ten calls. Booleans are the strings true or false.
Pagination in the Threads Profile Info Scraper API
The Threads Profile Info Scraper API is a single lookup: one call returns the whole result and there is no cursor to page through. A successful call costs 1 credit; failed calls cost 0.
Access Without Threads Login
The Threads Profile Info 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 Profile Info 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 Profile Info Scraper API.
- Public data only.
- A failed call, for example a missing or unavailable profile, 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. - 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 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 |
Errors and Retry Handling
| 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.
Retry logic for the Threads Profile Info Scraper API
import time, requests def get_profile(value, key, tries=5): for attempt in range(tries): r = requests.get( "https://proxy.scrapier.io/api/v2/threads-profile-info/", 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 | Profiles 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 Profile Info Scraper API
The Threads Profile Info Scraper API bills 1 credit per successful profile. 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 = ["trendspider"] # your list def fetch(value): r = requests.get( "https://proxy.scrapier.io/api/v2/threads-profile-info/", headers={"X-API-Key": "YOUR_API_KEY"}, params={"usernames": value}, timeout=210, ) r.raise_for_status() out = r.json()["data"]["result"] 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", "full_name", "follower_count", "is_verified", "biography", "text_post_app_is_private"] 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 Profile Info Scraper API
username,full_name,follower_count,is_verified,biography,text_post_app_is_private trendspider,TrendSpider,68011,true,Award-Winning 🏆 All-in-One Trading Platform.\nCharts, scans, backtests, alerts, AI tools, data & more.,false
AI Agent Access via MCP
MCP for the Threads Profile Info 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-profile-info. It takes the same usernames input and costs the same 1 credit per profile. Setup for every client is on the Threads Profile Info 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.resultfields to your columns
Loop and paginate
MCP tool in your agent
Call run_scrape with endpoint threads-profile-info 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 profile API?
Yes. Scrapier's Threads Profile Info Scraper API returns any public profile 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-profile-info/</code> with <code>params={'usernames': 'trendspider'}</code> and <code>headers={"X-API-Key": KEY}</code>. Read <code>r.json()["data"]["result"]</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 profiles 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 profiles as typed JSON in one request
1 credit per profile · failed calls free