Threads Search Users API
Scrape Threads Search Users data with one API call. Searches Threads for user accounts matching a query. Returns up to about 10 matching accounts with the handle, display name, avatar and verification status. A plain call is that identity window for 1 credit, and `author.followers`, `author.bio`, `author.private` and `author.ext.bio_link` stay null: the search index does not carry them. Send `include=profile` to fill them by row hydration: each account is looked up on `/v1/threads/profile` by its handle in the same call, and only those four leaves are copied onto the row, so nothing already on it changes. It costs 1 credit per account filled, adds 3 to 6 seconds (never more than 12), and a `data.hydration` block reports the rows looked up, filled and served from cache and the credits held and kept; an account the lookup could not fill is refunded and named by `data._warnings: ["profile_partial"]`. `limit` (1 to 12) takes the top N accounts and caps the extra credits with them. `include_details=true`, the older spelling, is the same call at the same price. Post count and join date stay null either way: Threads does not publish them. `author.url` is the account's Threads permalink, built from the handle.
Last updated September 2026Maintained by the SocialCrawl team
Returns Threads accounts matching a query, with handle, display name, avatar and verification status. Follower count, bio and the private flag stay null unless you send include=profile.
Use it to find accounts by name or topic; search looks for posts instead of people. Send include=profile when you need follower count and bio on the same rows, at 1 credit per account filled.
Searching 65 platforms in parallel
What can you do with the Search Users API?
The Search Users endpoint gives you structured Threads data with computed fields in a single request. No scraping infrastructure to build or maintain.
Example Request
curl -H "x-api-key: YOUR_API_KEY" \
"https://www.socialcrawl.dev/v1/threads/search/users?query=tech"import requests
response = requests.get(
"https://www.socialcrawl.dev/v1/threads/search/users",
params={
'query': 'tech',
},
headers={"x-api-key": "YOUR_API_KEY"},
)
data = response.json()const response = await fetch(
"https://www.socialcrawl.dev/v1/threads/search/users?query=tech",
{
headers: { "x-api-key": "YOUR_API_KEY" },
},
);
const data = await response.json();Parameters
| Parameter | Required | Description |
|---|---|---|
| query | Yes | Search keyword or phrase to find Threads users |
| include | No | Send `profile` to fill `author.followers`, `author.bio`, `author.private` and `author.ext.bio_link` on each account by looking it up on `/v1/threads/profile` in the same call. 1 credit per account filled from a fresh lookup (12 at most, or `limit`); accounts served from that lookup's cache (15 minutes) and accounts it could not fill are free. Adds 3 to 6 seconds, never more than 12. One token only: `profile`. (profile) |
| limit | No | Take the top N accounts of the page, 1 to 12. With `include=profile` it also caps the extra credits: `limit=5&include=profile` holds 6 credits, not 13. A plain call with `limit` still costs 1. |
| include_details | No | The older spelling of `include=profile`, kept working: `include_details=true` runs the same join at the same price (1 credit per account filled, 13 at most), and `false` is the plain call. Prefer `include=profile` in new code. |
What does the Threads Search Users API return?
Every response follows one unified schema. Here is a real, unmodified response body, so you can see the exact fields you get back before spending a credit.
Example response
{
"success": true,
"platform": "tiktok",
"endpoint": "/v1/tiktok/search/users",
"data": {
"items": [
{
"author": {
"id": "6780262640079193090",
"username": "cookingwithhel",
"display_name": "Cooking with Hel",
"avatar_url": "https://p19-common-sign.tiktokcdn-us.com/tos-alisg-avt-0068/e1547b843ed71ccc69e199147854f489~tplv-tiktokx-cropcenter-q:100:100:q70.heic?biz_tag=musically_user.user_cover&dr=8835&idc=useast8&ps=87d6e48a&refresh_token=7f24701a&s=SEARCH&sc=avatar&shcp=c1333099&shp=30310797&t=223449c4&x-expires=1783202400&x-signature=bLp06YEEM1DEDR6nG%2BZt3lhGWx4%3D",
"bio": null,
"verified": null,
"followers": 4214875,
"following": 1,
"posts_count": 2341,
"likes_count": 62731828,
"url": null,
"location": null
}
},
{
"author": {
"id": "7352666564073833515",
"username": "cooking_recipescr",
"display_name": "cooking_recipescr",
"avatar_url": "https://p19-common-sign.tiktokcdn-us.com/tos-useast5-avt-0068-tx/7352667004160966699~tplv-tiktokx-cropcenter-q:100:100:q70.heic?biz_tag=musically_user.user_cover&dr=8835&idc=useast8&ps=87d6e48a&refresh_token=6df0f827&s=SEARCH&sc=avatar&shcp=c1333099&shp=30310797&t=223449c4&x-expires=1783202400&x-signature=ysLi7%2FLtH4t5ebZnGzJXSfgYhnU%3D",
"bio": null,
"verified": null,
"followers": 1780390,
"following": 1,
"posts_count": 995,
"likes_count": 10060260,
"url": null,
"location": null
}
},
{
"author": {
"id": "6829580668634694662",
"username": "felizcooking",
"display_name": "Feliz Cooking",
"avatar_url": "https://p16-common-sign.tiktokcdn-us.com/tos-maliva-avt-0068/179d2c1fe2dc5523974abdaf232e8554~tplv-tiktokx-cropcenter-q:100:100:q70.heic?biz_tag=musically_user.user_cover&dr=8835&idc=useast8&ps=87d6e48a&refresh_token=97c11cfd&s=SEARCH&sc=avatar&shcp=c1333099&shp=30310797&t=223449c4&x-expires=1783202400&x-signature=aCkp4jy6AxdG2R9otN52rtXzHNc%3D",
"bio": null,
"verified": null,
"followers": 338243,
"following": 374,
"posts_count": 464,
"likes_count": 2140124,
"url": null,
"location": null
}
}
],
"next_cursor": "30",
"total": 30,
"dropped": 0
},
"credits_used": 1,
"credits_remaining": 9999,
"request_id": "req-8Kq2ZmR4vT9xLb3P",
"cached": false,
"pagination": {
"next_cursor": "sc.eyJ2IjoyLCJjIjoiMzAiLCJwIjoiY3Vyc29yIn0",
"has_more": true,
"page_size": 30
}
}Example captured from the TikTok API. Every SocialCrawl endpoint returns this same unified schema, so your Threads Search Users response has the same fields.
How does the Threads Search Users API work?
Send a GET request with your API key and get back clean, structured JSON in our unified schema. Supported computed fields are populated when the source provides the required inputs.
Method
GET
Response
JSON
How do you scrape social media data in seconds?
The fastest social media scraping API for developers. Scrape profiles, posts, comments, and analytics from 65 platforms covering 10B+ monthly active users.
One schema, every platform
Query 65 platforms with identical response structures. Write your integration once.
Computed fields, not just scraped
When an endpoint supports these metrics and the source provides the required inputs, the normalized record includes engagement_rate, estimated_reach, content_category, and language. Ready to use.
See your data before you code
Visual Data Explorer. Paste any URL, get rich result cards, sortable tables, CSV export.
import requests
response = requests.get(
'https://www.socialcrawl.dev/v1/tiktok/profile',
params={'handle': 'charlidamelio'},
headers={'x-api-key': 'sc_YOUR_API_KEY'}
)
data = response.json(){
"success": true,
"platform": "tiktok",
"data": {
"author": {
"username": "charlidamelio",
"followers": 152400000
},
"engagement": {
"likes": 12400000000,
"engagement_rate": 0.087
},
"metadata": {
"language": "en",
"content_category": "lifestyle"
}
}
}Have a question? We got answers
Find answers to frequently asked questions about SocialCrawl's API, pricing, and capabilities.
Contact usHow do I find Threads users by keyword?
What data does each user result include?
How is this different from searching posts?
Can I filter the results by verification or follower count?
How much does the Threads User Search API cost?
Ask AI about SocialCrawl
Ready to scrape Threads Search Users data?
Get your API key and start pulling Threads data in under 60 seconds.
