X / Twitter API
X / Twitter 搜索用户 API
按关键词搜索 X (Twitter) 账号，即 X 搜索中的“用户”标签页。匹配用户名、显示名称和主页简介，返回标准化的主页记录，包含粉丝数、关注数和帖子数，并支持游标分页。搜索帖子请用 twitter.search。
POST/v1/run/twitter.search_users
可用率
99.95%
30d · 8,539 次调用
请求数
8,600
30d · 按周，近 12 周
响应时间
1.4s
中位数 · 30d
服务商网络
按流量排序的服务商
试一试
发出你的第一个请求
示例响应
免费运行只返回前 3 条结果。为密钥充值即可获得完整响应。
{
"data": {
"nextCursor": "example",
"users": [
{
"avatarUrl": "https://example.com/image.jpg",
"bio": "A short example description of this item.",
"canDm": true,
"coverUrl": "https://example.com/page",
"createdUtc": 12.5,
"followers": 12500,
"following": 12500,
"id": "a1b2c3d4",
"listedCount": 12500,
"location": "example",
"name": "Example title",
"posts": 248,
"profileUrl": "https://example.com/page",
"username": "alex_rivera",
"verified": true
}
]
},
"found": true,
"reason": "not_found"
}响应类型定义
interface TwitterSearchUsersResponse {
data: {
nextCursor: string | null;
users: {
avatarUrl: string;
bio: string;
canDm?: boolean;
coverUrl?: string;
createdUtc: number;
followers: number;
following: number;
id: string;
listedCount?: number;
location: string;
name: string;
posts: number;
profileUrl: string;
username: string;
verified: boolean;
}[];
} | null;
found: boolean;
reason?: "not_found";
}完整的参数与响应参考：这个接口的每个字段、类型和示例。
参考
请求、响应与价格
最近验证于 2026-09-29 · 可用率和延迟按 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"}'| 字段 | 类型 | 示例值 |
|---|---|---|
| 请求体 | ||
| query | string | "ai agents"用于匹配 X (Twitter) 用户名、显示名称和主页简介的关键词。这是 X 搜索中的“用户”标签页：传入一个主题（'ai agents'）、一个名字（'Elon Musk'）或一个用户名（'openai'），返回的是账号而不是帖子。搜索帖子请用 twitter.search。 |
| cursor | string | 来自上一次响应 nextCursor 的不透明分页游标。第一页请省略；传入它以获取下一页账号。 |
| 响应 | ||
| 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[].canDm | boolean | Whether the account accepts direct messages. |
| data.users[].coverUrl | string | Profile banner image URL of the account. |
| 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[].listedCount | integer | Number of public lists the account appears on. |
| 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. |
| reason | "not_found" | Present only when `found` is false, and says why there is no result. `not_found`: the source states the target does not exist, or returned nothing for it. A `found: false` answer is a successful call, not an error, and `costUsd` is what it actually cost. |
| 价格 | ||
| 每次请求价格 | USD | US$0.00075 |
| 价格（/千次请求） | USD | US$0.75 |
常见问题
关于 X / Twitter 搜索用户 API
AnyAPI 的 X / Twitter 搜索用户 API 只需一次 POST 请求 /v1/run/twitter.search_users，就以统一格式的 JSON 返回 X / Twitter 数据。按关键词搜索 X (Twitter) 账号，即 X 搜索中的“用户”标签页。匹配用户名、显示名称和主页简介，返回标准化的主页记录，包含粉丝数、关注数和帖子数，并支持游标分页。搜索帖子请用 twitter.search。AnyAPI 会在 2 个数据源之间路由每个请求，某个数据源失败时自动切换。费用：每千次请求 US$0.75 起，以美元计价，无需订阅，也没有每月最低消费。过去 30 天，通过 AnyAPI 发起的 X / Twitter 搜索用户 API 调用中有 100.0% 成功，响应时间中位数为 1.4 秒，共测量 8,539 次调用。
费用：每千次请求 US$0.75 起，以美元计价，无需订阅，也没有每月最低消费。你只需为一个美元钱包充值，每次调用从中扣费。部分由钱包付费的失败请求会产生处理费用，我们按成本原价转嫁，不加价；错误响应会显示收取的金额。
按关键词搜索 X (Twitter) 账号，即 X 搜索中的“用户”标签页。匹配用户名、显示名称和主页简介，返回标准化的主页记录，包含粉丝数、关注数和帖子数，并支持游标分页。搜索帖子请用 twitter.search。响应是统一格式的 JSON，外层结构与每个 AnyAPI 接口相同，所以解析另一个接口只需换一个 URL，别的都不用改。
过去 30 天，通过 AnyAPI 发起的 X / Twitter 搜索用户 API 调用中有 100.0% 成功，响应时间中位数为 1.4 秒，共测量 8,539 次调用。这些是 AnyAPI 对经过网关的流量的自有测量，持续重新计算，并非公开承诺的服务等级目标。