Bilibili Details API
API health
- 24h health
- Normal
- 24h average time
- —
- Healthy / normal
- Available
- Limited
- Mostly down
Last 24 hours
Last 30 days
Look up a Bilibili uploader by numeric ID for name, bio, level, follower and video counts, verification title and premium membership. Pass only the integer from the space.bilibili.com link in user_id; their videos come from user_posts.
Bilibili Details reads one uploader's public profile from the numeric user_id: name, bio, avatar, gender, user level, follower and following counts, number of videos, verification status and title, and premium membership. It tells you who runs a channel and how established it is, which sponsorship teams, agencies and researchers check before they contact an uploader or add a channel to a watch list.
Store each profile with the date of the call, since the counts change over time. avatar_url can be a sized link that stops working, so save the image itself when you need it later. level, verified_title and is_vip describe an account's standing on the site rather than its reach, and video_count shows how much it has published. To see the uploads themselves, pass the same user_id to the Bilibili Posts by user capability.
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
Paste this into your AI assistant. It already holds this endpoint's parameters, response fields and an example request, so the assistant can ask what you need and then write the scraper.
Please help me write a data collection script with the EveryInfra Bilibili Details endpoint (bilibili/profile).
Endpoint contract:
- 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 bilibili and action to profile, and put the parameters inside params.
- Required parameters:
- user_id: Specifies a Bilibili uploader's numeric mid, extracted from https://space.bilibili.com/<mid>. Provide only the raw integer in user_id, without nicknames, BV IDs, or full space URLs.
- Returns one object. Main fields: user_id, name, url, bio, avatar_url, gender, level, follower_count, following_count, video_count, like_count, is_verified; 18 fields in total, full list at https://api.everyinfra.com/api/v1/social/catalog?platform=bilibili.
- Example request body:
{
"platform": "bilibili",
"action": "profile",
"params": {
"user_id": "946974"
}
}
- 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
| Name | In | Type | Required | Default | Description |
|---|---|---|---|---|---|
Authorization | header | string | Yes | - | Bearer followed by your API key. Create it in the console; never put it in a URL or a code repository. |
platform | body | string | Yes | bilibili | Platform identifier, fixed value. |
action | body | string | Yes | profile | Capability identifier, fixed value. |
user_id | body.params | Not declared | Yes | - | Specifies a Bilibili uploader's numeric mid, extracted from https://space.bilibili.com/<mid>. Provide only the raw integer in user_id, without nicknames, BV IDs, or full space URLs. |
Code samples
curl -X POST 'https://api.everyinfra.com/api/v1/social' \
-H "Authorization: Bearer $EVERYINFRA_API_KEY" \
-H 'Content-Type: application/json' \
--data-raw '{
"platform": "bilibili",
"action": "profile",
"params": {
"user_id": "946974"
}
}'[OpenAPI definition (JSON)]Samples read the key from the EVERYINFRA_API_KEY environment variable; copied code never contains your key.
Response example
Captured September 26, 2026 at 08:56 (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.
{
"id": "req_…",
"platform": "bilibili",
"action": "profile",
"results": {
"user_id": "946974",
"name": "影视飓风",
"url": "https://space.bilibili.com/946974",
"bio": "无限进步!|商务合作请联系邮箱:(已隐去)(邮件中麻烦备注公司、咨询内容)|店铺名:影视飓风",
"avatar_url": "https://i0.hdslb.com/(已隐去)",
"gender": "(已隐去)",
"level": 6,
"follower_count": 18402297,
"following_count": 686,
"video_count": 932,
"is_verified": true,
"verified_title": "2025百大UP主、2023年度最高人气奖UP主、课堂优质讲师",
"is_vip": true,
"vip_label": "十年大会员",
"birthday": "(已隐去)",
"platform": "bilibili",
"recent_videos": [
{
"id": "BV1J7hE6aEDQ",
"url": "https://www.bilibili.com/video/BV1J7hE6aEDQ",
"title": "比电影更夸张?专业保镖到底在做什么?",
"view_count": 6840704,
"comment_count": 6722,
"posted_at": "2026-09-22T09:00:00+00:00"
},
{
"id": "BV1cSec6tEux",
"url": "https://www.bilibili.com/video/BV1cSec6tEux",
"title": "选哪个?iPhone 18 Pro&Duo深度上手",
"view_count": 13290851,
"comment_count": 206473,
"posted_at": "2026-09-16T12:00:00+00:00"
},
{
"id": "BV17PYC6KEXu",
"url": "https://www.bilibili.com/video/BV17PYC6KEXu",
"title": "和五月天阿信见了他",
"view_count": 1874796,
"comment_count": 3815,
"posted_at": "2026-09-14T09:05:38+00:00"
}
]
},
"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.
| Field | Meaning |
|---|---|
user_id | User's unique ID on the platform. |
name | Name of the object itself, for account, product and business capabilities. |
url | Link to the record on the platform. |
bio | Profile bio written by the account; may contain line breaks and emoji. |
avatar_url | Avatar image link. Some platforms return sized CDN links that can expire. |
gender | Keeps the platform's own meaning |
level | Keeps the platform's own meaning |
follower_count | Followers. null means not disclosed, not 0. |
following_count | Accounts followed. null means not disclosed, not 0. |
video_count | Keeps the platform's own meaning |
like_count | Likes. null means the platform or this capability does not disclose it; it is not 0. |
is_verified | Whether the platform verified the account. null means it cannot be determined. |
verified_title | Keeps the platform's own meaning |
is_vip | Keeps the platform's own meaning |
vip_label | Keeps the platform's own meaning |
birthday | Keeps the platform's own meaning |
school | Keeps the platform's own meaning |
platform | Source platform identifier, the same as platform in the request (for example xiaohongshu, tiktok). |
recent_videos | Recently published videos, each with its title, link, view count, duration and so on; absent when there are none. |
FAQ
Where do I find an uploader's user_id?
Open the uploader's space page on Bilibili and read the address: the digits in https://space.bilibili.com/<mid> are the mid, and the mid is the user_id. Pass those digits alone. A nickname, a BV video ID or the full space link is not a valid value for this parameter.
What do level and verified_title tell me?
level is the account's Bilibili user level on a scale from 0 to 6. verified_title is the verification title shown on the profile, such as a well-known uploader label. Read both with is_verified, where null means the verification status could not be determined, not that the account is unverified.
Why is follower_count null for some uploaders?
A null follower_count means Bilibili did not disclose the figure for that account, not that the account has no followers. following_count and like_count work the same way. Keep these as missing values when you average or rank channels; filling them with zero drags every average down.
Errors and billing
- 401
- Missing or invalid key. Authentication runs before parameter checks, so unauthenticated requests never see the parameter schema.
- 422
- Wrong parameter name or value. The error lists the parameters and allowed values this capability accepts and the closest match; it happens before any charge.
- 402
- Insufficient balance. Top up first.
- 429
- The account's per-minute request limit was reached (all of its API keys count together; a key's own lower limit applies first). Wait for Retry-After and try again; a rate package in the console raises the limit.
- 503
- Could not complete right now. Any charge for the call goes back to your balance automatically, and the billing receipt in the response states the actual outcome, including when it is not yet known. Do not resend blindly.
- 200 empty
- The request completed without data and is not charged (billing.reason = empty_result_refunded).