Search Threads Accounts by Name or Username
View all Threads Public Data API endpoints →Pass a required query containing a name, username or account-search keyword. The response includes status, request_id and data.results, with candidate profiles at data.results[].node. Observed fields include username, string pk and id, full_name, is_verified, follower_count and profile_pic_url. Select the intended username before requesting its full profile or account posts: a similar display name is not proof of identity. A query for a nonexistent random username returned a successful response with data.results:[]. Treat an empty result array as no matches for that query, not as an outage or definitive proof that a particular account was deleted. Results are not an exhaustive account directory, and no pagination parameter is exposed.
API Features
Live API Demo
🔒 Sign in to try it live
Log in to call this API with your own API key. New accounts get 100 free credits — no card required.
Log in / Sign upNo active API key found. Create one in your Dashboard, then reload this page. Dashboard →
/api/project/threads-scraper/search-users API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/threads-scraper/search-users?key=<API_KEY>&query=zuck'
Query Result
Use Cases
- Account-picker interface: search a supplied name and display candidate handles and verification flags for human disambiguation.
- Brand-handle resolution: turn a company or spokesperson name into candidate usernames before enriching the chosen public profile.
- Preliminary creator shortlist: discover possible accounts from relevant terms, then manually review profiles and posts rather than assuming exhaustive coverage.
- Directory intake review: route ambiguous or empty account-search results to a researcher instead of automatically linking a similar display name to a customer record.
Frequently asked questions
Can I search with a person's name instead of an exact username?
Yes. query accepts a name, username or search keyword. Candidate accounts appear under data.results[].node. Use each returned username for subsequent profile or account-post requests.
Does a matching display name establish which account belongs to a person?
No. Similar names can refer to different accounts. Review the username, full_name, verification flag and other public context before selecting a candidate; search results alone do not establish identity or ownership.
Is an empty data.results array an error?
Not necessarily. A tested nonexistent username returned status:ok and data.results:[]. This is a valid no-match result for the query, not evidence of an outage or a definitive account-deletion finding.
Can I paginate user search to build a complete account directory?
No pagination input is exposed for user search. Treat the returned candidates as a query-specific selection, not an exhaustive directory, and do not send undocumented cursor or page parameters.