Threads

GET /v1/threads/search-users

Threads Search Users API

Find Threads profiles by keyword — username, display name, profile URL, and verified flag for each match.

~14 credits (0.7/result) per request

Try in Playground Get your API key — free Read the docs

TL;DR

Find Threads profiles by keyword — username, display name, profile URL, and verified flag for each match. The Threads Search Users API (Threads) is a single authenticated GET request to /v1/threads/search-users that responds with clean JSON and costs ~14 credits (0.7/result). Pass cache=true for a free 24h cache hit; default is always fresh. Start with 100 free credits — no credit card.

What is the Threads Search Users API?

Pass a keyword and the Threads Search Users API returns distinct Threads profiles related to that topic as clean JSON. Each result includes username, display name, a ready-to-open profile URL (threads.net/@handle), and whether the account is verified. This endpoint does not include follower counts or avatars — call Threads Profile with the returned URL or @handle for full profile stats. Use it to discover creators in a niche, turn a name into a confirmed @handle, or seed a lead list. Billed per result — about 0.7 credits each. Pass cache=true to serve from the 24h shared cache (0 credits on hit); default is always fresh.

What you get

Distinct Threads users matching your keyword
Username, display name, and verified flag
Canonical profile URL for each user
Pair with Threads Profile for followers and avatar

Try it

Open in Playground

Fill in the parameters below and copy a ready-to-run request, or open the live Playground to run it against your account (no API key paste).

Parameters

q*stringKeyword to find Threads users / creators (min 2 characters).limitoptionalintegerMax items to return (default 20, max 100). Billed per result.cacheoptionalbooleanSet true to serve from the 24h response cache. Default false — always fetch fresh data.

API keyoptionalPaste your key to get a ready-to-run snippet. It stays in your browser.Sign in to run live

curl "https://api.captapi.com/v1/threads/search-users?q=tech" \
  -H "Authorization: Bearer capt_live_..."
# or: -H "x-api-key: capt_live_..."

Edit the parameters and the code updates instantly. Switch languages and hit copy.

Example response

{
  "success": true,
  "data": {
    "query": "tech",
    "totalReturned": 5,
    "users": [
      {
        "username": "red.rose.whiterose",
        "displayName": null,
        "url": "https://www.threads.net/@red.rose.whiterose",
        "verified": false
      },
      {
        "username": "vulnarex",
        "displayName": null,
        "url": "https://www.threads.net/@vulnarex",
        "verified": false
      },
      {
        "username": "alina_intech",
        "displayName": "Alina",
        "url": "https://www.threads.net/@alina_intech",
        "verified": false
      },
      {
        "username": "eau.dreyy",
        "displayName": "O-Drey",
        "url": "https://www.threads.net/@eau.dreyy",
        "verified": true
      },
      {
        "username": "blkjenius",
        "displayName": "Jay D Miller",
        "url": "https://www.threads.net/@blkjenius",
        "verified": true
      }
    ]
  }
}

Billing metadata is returned in response headers: X-Captapi-Credits (credits charged), X-Captapi-Cache (hit or miss), and X-Captapi-Source. Failed requests (4xx/5xx) are never charged. See the full list of error codes in the error reference.

Response structure

A successful call returns success, cached, creditsUsed, and a data object with the following fields:

Top-level fields

queryThe search query you sent.
totalReturnedNumber of items returned in this response.

Users

Each item in users contains:

usernameAccount username / handle.
displayNameDisplay name of the account.
urlCanonical URL of the item.
verifiedWhether the account is verified.

Parameters

Name	Type	Required	Description
q	string	Yes	Keyword to find Threads users / creators (min 2 characters).
limit	integer	No	Max items to return (default 20, max 100). Billed per result.
cache	boolean	No	Set true to serve from the 24h response cache. Default false — always fetch fresh data.

Authentication: send your key as Authorization: Bearer capt_live_.... A typical call costs ~14 credits (0.7/result) — billed per result, so the exact amount scales with how many items you request. Pass cache=true for a free 24h cache hit; default is always fresh (metrics refresh within ~1 hour).

Using an AI agent? This endpoint is the MCP tool threads_search_users via @captapi/mcp. Set it up →

How it works

1. Sign up — get 100 free credits, no card required.
2. Create a key from your dashboard.
3. Send one request to /v1/threads/search-users and parse the JSON response.

Use cases

Trend Discovery

Find trending content by keyword or hashtag.

Content Sourcing

Build feeds and playlists programmatically.

Monitoring

Track topics, brands, and competitors.

Research

Sample large sets of content for analysis.

Frequently asked questions

What does the Threads Search Users API do?+

The Threads Search Users API lets you search and return matching results from a public Threads query using one GET request to /v1/threads/search-users. It returns clean JSON — no OAuth or infrastructure setup required.

How many credits does the Threads Search Users API cost?+

At the default limit this endpoint costs 14 credits (0.7 per result). Billing scales with how many results you request. Pass cache=true to serve from the 24h shared cache (0 credits on hit); default is always fresh. Failed or empty results are never charged.

Do I need a Threads API key or OAuth?+

No. A single Captapi key works across every platform Captapi supports — YouTube, TikTok, Instagram, Facebook, Twitter/X, Reddit, Threads, Bluesky, Pinterest, LinkedIn, Rumble, Spotify, Kwai, and more. We handle proxies, rate limits, retries, and authentication for you.

Is the Threads Search Users API suitable for production use?+

Yes. It is a stable REST endpoint with predictable JSON and automatic retries. Pass cache=true to serve from the 24h shared cache (0 credits on hit); default is always fresh. Use it for analytics, monitoring, and content automation.

More Threads APIs

Threads Profile API Threads User Posts API Threads Post Details API Threads Post Search API

Ready to use the Threads Search Users API?

Get started free