Bilibili Search API

POST

API health

24h health
100%
24h average time
12.97 s
Last checked
September 26, 2026 at 18:04 (UTC)
  • Healthy / normal
  • Available
  • Limited
  • Mostly down
Health APIHealthy
How health is measured
  • Health = the share of calls that returned data, in percent. Empty results, failures and unknown outcomes do not count as returning data.
  • Levels: 90% and above is healthy, 70% and above is available, 40% and above is limited; anything lower is mostly down.
  • A period (the last 24 hours, one hour or one day) gets a score only once it has at least 50 calls. Periods with fewer calls show as normal: a few failures among a handful of calls do not mean the API is down.
  • Calls include real customer calls and our own daily probe calls. Request errors (wrong parameters, no balance) are excluded.
  • Average time counts only calls that completed normally: response time for sync calls, acceptance to completion for async ones.
By period
Time (UTC)StatusHealthAverage time
2026-09-26 18:00 - 18:59Normal——
2026-09-26 17:00 - 17:59Normal——
2026-09-26 16:00 - 16:59Normal——
2026-09-26 15:00 - 15:59Normal——
2026-09-26 14:00 - 14:59Normal——
2026-09-26 13:00 - 13:59Normal——
2026-09-26 12:00 - 12:59Normal——
2026-09-26 11:00 - 11:59Normal——
2026-09-26 10:00 - 10:59Normal——
2026-09-26 09:00 - 09:59Normal——
2026-09-26 08:00 - 08:59Normal——
2026-09-26 07:00 - 07:59Normal——
2026-09-26 06:00 - 06:59Normal——
2026-09-26 05:00 - 05:59Normal——
2026-09-26 04:00 - 04:59Normal——
2026-09-26 03:00 - 03:59Healthy100%12.97 s
2026-09-26 02:00 - 02:59Normal——
2026-09-26 01:00 - 01:59Normal——
2026-09-26 00:00 - 00:59Normal——
2026-09-25 23:00 - 23:59Normal——
2026-09-25 22:00 - 22:59Normal——
2026-09-25 21:00 - 21:59Normal——
2026-09-25 20:00 - 20:59Normal——
2026-09-25 19:00 - 19:59Normal——
2026-09-26Healthy100%12.97 s
2026-09-25Normal——
2026-09-24Normal——
2026-09-23Normal——
2026-09-22Normal——
2026-09-21Normal——
2026-09-20Normal——
2026-09-19Normal——
2026-09-18Normal——
2026-09-17Normal——
2026-09-16Normal——
2026-09-15Normal——
2026-09-14Normal——
2026-09-13Normal——
2026-09-12Normal——
2026-09-11Normal——
2026-09-10Normal——
2026-09-09Normal——
2026-09-08Normal——
2026-09-07Normal——
2026-09-06Normal——
2026-09-05Normal——
2026-09-04Normal——
2026-09-03Normal——
2026-09-02Normal——
2026-09-01Normal——
2026-08-31Normal——
2026-08-30Normal——
2026-08-29Normal——
2026-08-28Normal——

Search public results on Bilibili. Accepts these parameters: keyword and sort. Returns these fields: favorite_count, title, duration_text, and view_count.

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.

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.
platformbodystringYesbilibiliPlatform identifier, fixed value.
actionbodystringYessearchCapability identifier, fixed value.
keywordbody.paramsNot declaredYes-Specifies video search terms for Bilibili based on titles or topics, rather than an exact uploader nickname search. Use user_id to query uploader profiles or user submissions.
sortbody.paramsenumNo-Specifies the video sort order with mapped values: relevance, newest for latest, most_viewed for view count, most_commented for comment relevance, and most_liked for favorites. This video sort mapping does not guarantee comment sorting by popularity or time on the comments endpoint, which requires separate verification.Allowed valuesmost_commentedmost_likedmost_viewednewestrelevance
limitbody.paramsinteger (1–50)No20

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": "bilibili",
  "action": "search",
  "params": {
    "keyword": "摄影入门"
  }
}'

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

Response example

Real response

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; the list keeps the first 2. id, billing and quota differ on every call, so only their shape is shown.

json
{
  "id": "req_…",
  "platform": "bilibili",
  "action": "search",
  "results": [
    {
      "id": "BV1pv411H78e",
      "url": "https://www.bilibili.com/video/BV1pv411H78e",
      "title": "从零开始手把手教你学摄影,20节课带你从小白到大师 | 摄影前期拍摄入门教程",
      "text": "此课程是一套面向零基础小白的零基础摄影前期拍摄系统教程,分为4大部分,一共20节,由浅入深。课程从器材讲解到参数技巧,最后带领大家实战拍摄,可以快速带大家入门摄影,录制于2020年,因故未能发布,现在作为福利分享给大家~\r\n\r\nPS: 如果大家觉得有帮助的话,求个一键三连~\r\n\r\nPART1 知己知彼——认识你的器材\r\nPART2 基础入门——学懂枯燥的参数\r\nPART3 技能提升——拍摄技巧全解\r\nPART4 综合运用——带你复盘拍摄现场",
      "duration_seconds": 28849,
      "duration_text": "480:49",
      "view_count": 8307391,
      "like_count": 301661,
      "comment_count": 3799,
      "danmaku_count": 38430,
      "favorite_count": 752984,
      "thumbnail_url": "https://i1.hdslb.com/bfs/archive/d293a1682ffac131d109bd6180c4df644f632388.png",
      "posted_at": "2021-07-02T03:56:53+00:00",
      "category": "数码",
      "author_name": "(已隐去)",
      "author_id": "(已隐去)",
      "author_url": "https://space.bilibili.com/(已隐去)",
      "platform": "bilibili",
      "tags": [
        "教程",
        "摄影",
        "相机"
      ]
    },
    {
      "id": "BV1MceuzVEz7",
      "url": "https://www.bilibili.com/video/BV1MceuzVEz7",
      "title": "【吊打付费】目前B站最完整的摄影教程,包含了所有干货内容!这还没人看,我不更了!!!",
      "text": "一个冷知识:点赞是免费的!但是可以让辛苦做视频的UP主开心快乐一整天!!!\n 我给大家准备了摄影礼包,评论“666”即可得",
      "duration_seconds": 71221,
      "duration_text": "1187:1",
      "view_count": 2186277,
      "like_count": 50942,
      "comment_count": 12382,
      "danmaku_count": 6525,
      "favorite_count": 124107,
      "thumbnail_url": "https://i2.hdslb.com/bfs/archive/5fffaef73d60995cf40a9336b58fe68b15ca5033.jpg",
      "posted_at": "2025-08-20T09:20:00+00:00",
      "category": "数码",
      "author_name": "(已隐去)",
      "author_id": "(已隐去)",
      "author_url": "https://space.bilibili.com/(已隐去)",
      "platform": "bilibili",
      "tags": [
        "摄影入门",
        "新手摄影",
        "零基础学摄影"
      ]
    }
  ],
  "count": 17,
  "billing": { … },
  "quota": { … }
}

Response fields

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

FieldMeaning
idThe record's unique ID on the source platform. Unique only within one platform; IDs can repeat across platforms.
urlLink to the record on the source platform.
titleTitle. null when the platform has no titles (for example text-only posts).
textBody text with HTML removed. Long text may be truncated.
duration_secondsDuration in seconds. null for content that is not video or audio.
duration_textKeeps the platform's own meaning
view_countViews or plays. null means not disclosed, not 0.
like_countLikes. null means the platform or this capability does not disclose it; it is not 0.
comment_countComments. null means not disclosed, not 0.
danmaku_countKeeps the platform's own meaning
favorite_countKeeps the platform's own meaning
coin_countKeeps the platform's own meaning
share_countShares. null means not disclosed, not 0.
thumbnail_urlThumbnail link, lower resolution than image_url.
posted_atPublish time in ISO 8601, UTC (for example 2026-08-07T12:34:56+00:00). Non-standard strings from the platform are passed through as is, so parse defensively. null means the platform does not disclose it.
categoryCategory name in the source platform's own taxonomy, not normalized across platforms.
author_nameAuthor's display name.
author_idAuthor's unique ID on the source platform.
author_urlLink to the author's profile on the source platform.
platformSource platform identifier, the same as platform in the request (for example xiaohongshu, tiktok).
tagsArray of tags. An empty array, not null, when there are none.

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
Per-minute request limit reached. Wait for Retry-After and try again.
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).