Silkline Data / Bilibili API / Search videos by keyword
Real run · 2026-11-09 · 10 records

Bilibili Search videos by keyword API

Search videos by keyword from Bilibili, returned as JSON rows you can save to CSV.

Resultready
JSON
10records in this run
22fields per record
8srun time, start to finish
$0.00736per record, Bronze tier
What it returns

Bilibili videos: search, details, popular, favourites (modes search, video, creator, popular, favorites)

Field Description
bvid Video ID (BV...)
title Video title
views View count
likes Like count
coins Coins given by viewers (mode video only)
favorites Times added to favorites
shares Share count (mode video only)
comments Comment count
danmaku Danmaku count
publishedAt Publish time, ISO 8601 UTC
durationSeconds Video length in seconds
authorName, authorId, authorUrl, authorAvatar Uploader's name, user ID, profile link and avatar URL (avatar where the source provides it)
category, tags Category (filled for search results) and tags (filled for search results and mode video)
description Video description, empty when the uploader wrote none
url, coverUrl, aid Video link, cover image URL and legacy numeric video ID
collectorUid, folderId, folderTitle, favoritedAt Mode favorites only: whose folder, the folder, and when the video was saved (ISO 8601 UTC)
Request

The input that produced this run

Mode search. Parameters as sent, with what each one does.

ParameterValueWhat it does
mode"search"What to scrape: search videos by keyword, details of specific videos, comments of videos, danmaku (on-screen comments) of videos, subtitles (full transcripts) of videos, creator profiles with their recent videos, a...
keyword"原神"Search keyword. Chinese keywords return the best results.
maxResults10Maximum number of items to return in total for this run (for the trending board, at most 50 words). You are charged per item returned.
Response fields

22 fields in every video

From the first record of the run above. Identity fields of ordinary users are masked on this site.

FieldTypeExample
typestrvideo
bvidstrBV1S2Wp6kE2x
aidint117582615025816
urlstrhttps://www.bilibili.com/video/BV1S2Wp6kE2x
titlestr笑死!薇斯纳不讲武德偷袭旅行者,被女皇惩罚了!还要咱代替女皇来检阅冬契军?真常务副冰神说是【原神冰宫密令】
descriptionnullnull
authorNamestr<masked>
authorIdstr<masked>
authorUrlstr<masked>
authorAvatarstr<masked>
coverUrlstrhttps://i0.hdslb.com/bfs/archive/965361b40d22f5a02131a5e6...
durationSecondsint249
publishedAtstr2026-11-08T20:08:47Z
viewsint34378
likesint458
coinsnullnull
favoritesint188
sharesnullnull
commentsint232
danmakuint14
categorystr手机游戏
tagslist["剧情", "RPG", "二次元", "坏灭肇始之时", "冰宫密令", "薇斯纳", "不讲武德", "原神",
Sample output

A real run, 22 fields per record

Run on 2026-11-09 with input {"mode": "search", "keyword": "原神", "maxResults": 10}. Personal fields of ordinary users are masked here.

titlelikescommentsviewsdurationSecondspublishedAt
笑死!薇斯纳不讲武德偷袭旅行者,被女皇惩罚了!还要咱代替女皇来检阅冬契军?真常务副冰神说是【原神冰宫密令】458232343782492026-11-08T20:08:47Z
如果说原神也拿到了隔壁记忆战舰的剧本,会怎么样呢?大胆揣测强度格局12610547304752026-11-08T09:13:21Z
【原神/4K】7.2版本-主线「坏灭肇始之时」全剧情流程(已完结)95110778518149412026-11-04T04:21:57Z
【原神】长峡深处的晶石城·上/至冬7.2开图主线①/不可使一切江河干涸/晶流与石箱的古歌谣·第一章/新基捷城见闻笔...29108133997070212092026-11-04T03:38:49Z
【原神七神】⚡为神何惧应天谴,我等本该《与天齐》⚡5174201333101402026-11-08T07:31:05Z
吐槽原神7.2主线剧情 气笑了!反叛天理有正当性吗?回答我!4924774601736572026-11-09T03:00:00Z
All 22 fields in one record
  • type video
  • bvid BV1S2Wp6kE2x
  • aid 117582615025816
  • url https://www.bilibili.com/video/BV1S2Wp6kE2x
  • title 笑死!薇斯纳不讲武德偷袭旅行者,被女皇惩罚了!还要咱代替女皇来检阅冬契军?真常务副冰神说是【原神冰宫密令】
  • description
  • authorName
  • authorId
  • authorUrl
  • authorAvatar
  • coverUrl https://i0.hdslb.com/bfs/archive/965361b40d22f5a02131a5e6...
  • durationSeconds 249
  • publishedAt 2026-11-08T20:08:47Z
  • views 34378
  • likes 458
  • coins
  • favorites 188
  • shares
  • comments 232
  • danmaku 14
  • category 手机游戏
  • tags
Pricing

What one video costs

Result · one video, comment, reply, danmaku, creator video, dynamic, trending word, live room, show (season) · $0.00736 · $0.00664 · $0.006

Full Bilibili price table and calculator

Developers

Run this request yourself

The same input as above, three ways.

Request
Response · 200application/json