Search accounts
Accounts matching a name or keyword: the first page of results, with follower counts as Weibo displays them in search, rounded. user-profile gives the exact figure. 1 credit.
/search-users Search & trending https://api.fetchlayer.dev/weibo/search-users Headers
Authorization string required Bearer token — your FetchLayer API key.
Parameters
query string required A name or keyword, up to 100 characters.
limit integer optional Maximum accounts returned, up to 50, or -1 for the maximum. (default: 20)
format string optional json or markdown, lowercase; any other value is a 400. Over MCP, markdown returns the result rendered as text; the REST API accepts it and returns JSON. (default: json)
timeoutMs integer optional Time limit for the whole request, in milliseconds (1000–120000); a value outside that range is a 400. When it runs out, a paged request returns what it has with nextCursor, billed for the pages it read; a request with nothing to return yet fails with a 503 you can retry, marked with the response header X-Timeout-Source: caller.
Response Fields
search-users
Search accounts
transport string The data source: always the platform id, "weibo".
scrapedAt string When the result was produced (ISO 8601).
notes string[] Caveats you can act on: a list that ends where Weibo stops showing more, long posts shortened in a list, paid placements left out. Empty when there are none. An empty result always comes with a note explaining it.
skippedRecords object[] Records Weibo sent that could not be read, each as { id, reason, fieldsPresent }; id may be null. Normally empty. One unreadable record never costs the rest of the response or the cursor.
pagesFetched number Full pages of results returned, minimum 1 — 20 comments or replies, 50 search posts, 48 media posts — which is what the request costs: one credit each.
query string The search term.
users object[] The matching accounts, in Weibo’s order.
users[].id string The account’s numeric id, which user-profile and user-posts accept.
users[].screenName string The display name.
users[].url string Link to the profile.
users[].avatarUrl string | null Avatar image.
users[].verified boolean Whether Weibo shows a verification badge.
users[].verifiedReason string | null Weibo’s verification text, such as 新浪科技官方微博, or null.
users[].followersCount number | null Followers as an exact figure where Weibo publishes one here, else null. user-profile always has the exact figure.
users[].followersCountText string | null Followers as Weibo displays them, rounded (2380万 is 23.8 million).
users[].description string | null The bio.
users[].postsCount number | null Posts the account has made.
users[].gender string | null male or female, as the account states it.
userCount number How many accounts are in this response.
Request
curl -X POST "https://api.fetchlayer.dev/weibo/search-users" \
-H "Authorization: Bearer ss-your-key" \
-H "Content-Type: application/json" \
-d '{"query":"华为","limit":20}'Response
{
"transport": "weibo",
"skippedRecords": [],
"scrapedAt": "2026-10-15T15:24:50.000Z",
"notes": [
"Follower counts in search results are rounded the way Weibo displays them (followersCountText); user-profile returns the exact figure."
],
"pagesFetched": 1,
"query": "华为",
"users": [
{
"id": "1839167003",
"screenName": "华为终端",
"url": "https://weibo.com/u/1839167003",
"verified": true,
"verifiedReason": "华为终端官方微博",
"followersCount": null,
"followersCountText": "2427.7万",
"description": "华为终端产品信息官方发布平台。",
"postsCount": 29798,
"gender": "male"
}
],
"userCount": 20
}