Search public Threads accounts. The response carries exactly the fields the answering upstream query supplies, typically username, user id, full name, profile image and verification status, and for some responses also a biography and friendship status. Fields the upstream does not supply are omitted rather than filled in. No result count is documented because the upstream page size is not fixed. Follower counts are not part of this endpoint; use the profile endpoint for those.
Run this endpoint
Endpoint
Parameters
Start with the required fields, then add optional filters only when your use case needs them.
Runnable path
1 required parameter needed before sending a request.
string
Required
Name, handle fragment, or keyword to match accounts by.
nasa
Response Schema
Example response fields are illustrative; inspect the JSON before integrating.
Example response fields
Scan these fields before integrating.
meta
users
search_parameters
Common users fields
pk
username
full_name
is_verified
{
"meta": {
"attempts": 1,
"duration_ms": 700,
"endpoint_family": "threads_search_users"
},
"users": [
{
"pk": "17841400000000000",
"username": "nasa",
"full_name": "NASA",
"is_verified": true
}
],
"search_parameters": {
"query": "nasa",
"engine": "threads_search_users"
}
}Errors
Handle these documented responses before retrying or showing customer-facing failures.
Not Found
Returned, and not billed, when the handle, post code or hashtag does not exist or is not publicly available.
Validation Error
Returned, and not billed, when a parameter is missing or outside its allowed range.
Service Unavailable
A retryable, non-billable failure. The upstream returned a degraded or unreadable response, or the request budget ran out.
Generate Code with AI
Copy a ready-made prompt with all the endpoint details, parameters, and example responses. Paste it into ChatGPT, Claude, or any AI assistant to instantly generate working code.
Try It Live
Test this endpoint in our interactive playground with real data.