POST

API health

24h health
Normal
  • Healthy / normal
  • Available
  • Limited
  • Mostly down
Normal

Last 24 hours

Last 30 days

Look up a Weibo user by numeric UID or /u/ profile link. Get display name, bio, gender, follower, following and post counts, and any verification note. Handles are not accepted, and the badge does not vouch for the person. Follower lists are not included.

Send POST https://api.everyinfra.com/api/v1/social with platform set to weibo and action set to profile. Price $0.56 per 1,000 requests ($0.000556 per call). Failed calls and empty results are not charged. Synchronous. For slow jobs add "mode": "async" to the body, take the job_id and poll.

AI prompt

#
Please help me write a data collection script with the EveryInfra Weibo Details endpoint (weibo/profile).

How the endpoint works:
- Request: POST https://api.everyinfra.com/api/v1/social with the header Authorization: Bearer <API key>. Read the key from the EVERYINFRA_API_KEY environment variable and never hard-code it.
- In the request body, set platform to weibo and action to profile, and put the parameters inside params.
- Required parameters:
  - user_id: Specifies the target Weibo user via their numeric UID or a profile URL containing /u/numeric_UID for the profile action.
- Returns one object. Main fields: user_id, display_name, url, bio, gender, follower_count, following_count, post_count, is_verified, verified_reason (Verification description of the account…), avatar_url, cover_image_url; 14 fields in total, full list at https://api.everyinfra.com/api/v1/social/catalog?platform=weibo.
- Example request body:
{
  "platform": "weibo",
  "action": "profile",
  "params": {
    "user_id": "1749127163"
  }
}
- Price: $0.56 per 1,000 requests; failed and empty results are not charged.
- For dozens or hundreds of targets, add "mode": "async" to the body: you get a job_id at once and poll GET https://api.everyinfra.com/api/v1/jobs/{job_id} for the result.
- On 422, fix the request using the suggested parameter names and allowed values in the error; on 429 or 503, wait for Retry-After and try again.

Before writing code, ask me which targets I need, how many, which fields, and what output format I want; then confirm the plan and the rough cost with me.

Request parameters

#
NameInTypeRequiredDefaultDescription
AuthorizationheaderstringYes-Bearer followed by your API key. Create it in the console; never put it in a URL or a code repository.
platformbodystringYesweiboPlatform identifier, fixed value.
actionbodystringYesprofileCapability identifier, fixed value.
user_idbody.paramsstringYes-Specifies the target Weibo user via their numeric UID or a profile URL containing /u/numeric_UID for the profile action. Username handles are not supported, and profile metadata does not include a full list of the user's posts.

Code samples

#
bash
curl -X POST 'https://api.everyinfra.com/api/v1/social' \
  -H "Authorization: Bearer $EVERYINFRA_API_KEY" \
  -H 'Content-Type: application/json' \
  --data-raw '{
  "platform": "weibo",
  "action": "profile",
  "params": {
    "user_id": "1749127163"
  }
}'

OpenAPI definition (JSON)Samples read the key from the EVERYINFRA_API_KEY environment variable; copied code never contains your key.

Response example

#
Captured October 24, 2026 at 18:28 (UTC) by calling this API with the parameters in the code sample above. results and count are that call's real response with personal information (names, handles, avatars, profile links, contact details) removed. id, billing and quota differ on every call, so only their shape is shown.
json
{  "id": "req_…",  "platform": "weibo",  "action": "profile",  "results": {    "user_id": "1749127163",    "display_name": "•••",    "url": "https://weibo.com/u/1749127163",    "bio": "小米董事长,金山软件董事长。业余爱好是天使投资。",    "gender": "•••",    "follower_count": 27336563,    "following_count": 1647,    "post_count": 22207,    "is_verified": true,    "verified_reason": "小米创办人,董事长兼CEO;金山软件董事长;天使投资人。",    "avatar_url": "https://tvax4.sinaimg.cn/•••",    "cover_image_url": "https://wx2.sinaimg.cn/crop.0.0.640.640.640/001Un9Srly1hrwga69ms4j60u00u0tas02.jpg",    "created_at": "2010-05-31T15:07:59+00:00",    "platform": "weibo"  },  "billing": {    "charged": …,    "charged_usd": …,    "balance_after_usd": …,    …  },  "quota": { … }}

Response fields

#

Business data is in results. The table lists the fields a record can contain; values the platform does not show are never made up.

FieldMeaning
user_idUser's unique ID on the platform.
display_nameDisplay name; can differ from username.
urlLink to the record on the platform.
bioProfile bio written by the account; may contain line breaks and emoji.
genderKeeps the platform's own meaning
follower_countFollowers. null means not disclosed, not 0.
following_countAccounts followed. null means not disclosed, not 0.
post_countTotal posts. null means not disclosed, not 0.
is_verifiedWhether the platform verified the account. null means it cannot be determined.
verified_reasonVerification description of the account (user_search).
avatar_urlAvatar image link. Some platforms return sized CDN links that can expire.
cover_image_urlKeeps the platform's own meaning
companyKeeps the platform's own meaning
created_atCreation time, same format as posted_at.
platformSource platform identifier, the same as platform in the request (for example xiaohongshu, tiktok).

Errors and billing

#
401
Missing or invalid key.
402
Insufficient balance. Top up first.
422
Invalid parameter name or value. Fix it using the suggestions in the error. No charge.
429
Per-minute request limit reached. Wait for Retry-After, then try again.
503
Could not complete. The held charge is returned to your balance. If the outcome is unknown, verify it before you retry.
200 empty
No data. No charge.

Errors

Official references

#

Used only to check objects and terms. They do not imply authorization or endorsement of EveryInfra by the platform.

  • Weibo: Definitions of UID, Nickname, and Followed Counts ↗

    Official Weibo documentation defines `uid` / `screen_name` as user ID / nickname, `friends_count` as followed count, and `followers_count` as follower count. Nickname query options in official APIs do not mean the `user_id` on this page supports nickname resolution; the fields returned are the ones documented here and depend on actual results.

    Checked 2026-09-04

Our own visit stats are always on. Google Analytics loads only if you choose “Allow analytics”. Privacy policy