Catalog/X / Twitter/Search users

POST

X / Twitter Search users API

/v1/run/twitter.search_users

Category SocialRequests / mo 29Routing 2 lanes · auto failover

Get ~100 free requests

Provider network

Providers ranked by traffic

click a provider for traffic and endpoints · routing stays automatic

Request

Gateway request

discovered operation

↓

Router

↓

Providers · 2

Capybara23 served82.14% uptime1857ms p5082.14% (28 calls)1857ms (23 calls)23$0.75/1k reqflat

Badger1 served16.67% uptime320ms p5016.67% (6 calls)320ms (1 call)1$0.189/1k resultsup to $0.00378 / request

↳ Calls hit the first lane first; on timeout or 5xx we retry down the ladder. Fallback order: Capybara → Badger

Try it

Make your first request

run it free, no key · same shape for every API

query*stringKeyword to match against X (Twitter) handles, display names, and profile bios. This is the People tab of X search: pass a topic ('ai agents'), a name ('Elon Musk'), or a handle ('openai') and get back accounts, not posts. Use twitter.search for posts.cursorstringOpaque pagination cursor from a previous response's nextCursor. Omit for the first page; pass it to fetch the next page of accounts.

Open in

Get a free key

Sample response

Free runs return only the first 3 results. Fund a key to get the full response.

{
  "data": {
    "nextCursor": "example",
    "users": [
      {
        "avatarUrl": "https://example.com/image.jpg",
        "bio": "A short example description of this item.",
        "createdUtc": 12.5,
        "followers": 12500,
        "following": 12500,
        "id": "a1b2c3d4",
        "location": "example",
        "name": "Example title",
        "posts": 248,
        "profileUrl": "https://example.com/page",
        "username": "alex_rivera",
        "verified": true
      }
    ]
  },
  "found": true
}

Response interface

interface TwitterSearchUsersResponse {
  data: {
    nextCursor: string | null;
    users: {
      avatarUrl: string;
      bio: string;
      createdUtc: number;
      followers: number;
      following: number;
      id: string;
      location: string;
      name: string;
      posts: number;
      profileUrl: string;
      username: string;
      verified: boolean;
    }[];
  } | null;
  found: boolean;
}

Full parameter and response reference - every field, type, and example for this endpoint.

Reference

Request, response, and price

Last verified 2026-08-23 · uptime and latency measured over 30d

POST /v1/run/twitter.search_users

curl -X POST https://api.getanyapi.com/v1/run/twitter.search_users \
  -H "Authorization: Bearer $ANYAPI_KEY" \
  -H "Content-Type: application/json" \
  -d '{"query":"ai agents"}'

Field	Type	Example value
Request body
query	string	"ai agents"Keyword to match against X (Twitter) handles, display names, and profile bios. This is the People tab of X search: pass a topic ('ai agents'), a name ('Elon Musk'), or a handle ('openai') and get back accounts, not posts. Use twitter.search for posts.
cursor	string	Opaque pagination cursor from a previous response's nextCursor. Omit for the first page; pass it to fetch the next page of accounts.
Response
data	object	The page of matching accounts, or null when nothing was found.
data.nextCursor	string	Opaque cursor for the next page of accounts, or null when this lane has no more. Pass it back as cursor to continue.
data.users	object[]	Matching X (Twitter) accounts, normalized to a compact profile record. Populated whenever the provider has data for the entity.
data.users[].avatarUrl	string	URL of the account's profile image. Populated whenever the provider has data for the entity.
data.users[].bio	string	The account's profile bio/description (may be empty).
data.users[].createdUtc	number	UTC epoch timestamp in seconds (Unix time). Multiply by 1000 for a JS Date in milliseconds.
data.users[].followers	integer	How many followers this account has.
data.users[].following	integer	How many accounts this account follows.
data.users[].id	string	The account's numeric X user id. Populated whenever the provider has data for the entity.
data.users[].location	string	The account's self-reported location (may be empty).
data.users[].name	string	The account's display name. Populated whenever the provider has data for the entity.
data.users[].posts	integer	How many posts this account has published.
data.users[].profileUrl	string	Canonical URL of the account's X profile. Populated whenever the provider has data for the entity.
data.users[].username	string	The account's @ handle, without the @ prefix. Populated whenever the provider has data for the entity.
data.users[].verified	boolean	Whether the account carries the blue verification check.
found	boolean	True when the search returned at least one account; false when nothing matched.
Price
Price per request	USD	$0.00075
Price /1k req	USD	$0.75

FAQ

About the X / Twitter Search users API

The AnyAPI X / Twitter Search users API returns X / Twitter search users data as normalized JSON from one POST call to /v1/run/twitter.search_users. Search X (Twitter) accounts by keyword - the People tab of X search. Matches handles, display names, and profile bios, and returns normalized profile records with follower, following, and post counts plus cursor pagination. Use twitter.search for posts. AnyAPI routes each request across 2 sources and falls back automatically when one fails. It costs from $0.75 per 1,000 requests, in US dollars with no subscription and no monthly minimum. Over the last 30 days, 82.8% of X / Twitter search users calls through AnyAPI succeeded, with a median response time of 1.9 seconds across 29 measured calls.

It costs from $0.75 per 1,000 requests, in US dollars with no subscription and no monthly minimum. You fund one USD wallet, each call draws it down, and a failed request costs $0.

Search X (Twitter) accounts by keyword - the People tab of X search. Matches handles, display names, and profile bios, and returns normalized profile records with follower, following, and post counts plus cursor pagination. Use twitter.search for posts. The response is normalized JSON with the same envelope every AnyAPI endpoint returns, so parsing a second endpoint is a change of URL and nothing else.

Over the last 30 days, 82.8% of X / Twitter search users calls through AnyAPI succeeded, with a median response time of 1.9 seconds across 29 measured calls. These are AnyAPI's own measurements of traffic through the gateway, recomputed continuously, not a published service-level target.

More to call

Other X / Twitter endpoints

Profile · from $0.18 /1k req User tweets · from $0.1818 /1k results Tweet · from $0.18 /1k req Article · from $0.75 /1k req Community · from $0.18 /1k req Community tweets · from $2.00 /1k req Followers · from $0.75 /1k req Following · from $0.75 /1k req Replies · from $0.75 /1k req Search · from $0.75 /1k req Search communities · from $0.198 /1k results Thread · from $5.00 /1k req Trends · from $0.18 /1k req Tweet transcript · from $2.00 /1k req User posts · from $0.75 /1k req

Get started

Two ways to start on AnyAPI

Humans fund a USD wallet and pay per request. Agents point a coding agent at one URL and onboard themselves.

Get ~100 free requests

Works with

Providers ranked by traffic

Make your first request

Request, response, and price

About the X / Twitter Search users API

How much does the X / Twitter Search users API cost?

What does the X / Twitter Search users API return?

How reliable is the X / Twitter Search users API?

Other X / Twitter endpoints

Two ways to start on AnyAPI