Bilibili Search Scraper API
A Bilibili search page is a JavaScript-heavy listing of videos, creators and engagement numbers.
This API takes a search URL on bilibili.tv, renders it in a headless browser behind rotating residential proxies, and returns either the rendered HTML or a JSON object you define. You supply the URL and your extraction logic; the service handles browser management, proxy rotation and anti-blocking.
What comes back from a Bilibili search page
> Each search result carries the video title, the creator handle, the view count, the upload date, the video length and the tag list. Those are the fields the page exposes, and they arrive parsed when you ask for structured output. If you would rather parse yourself, request rendered HTML and read the DOM directly. The two output modes are not interchangeable in effort: JSON mode moves selector or natural-language extraction into the request, while HTML mode leaves parsing to your code.
Three workflows this fits
The common jobs map cleanly onto the same endpoint:
- Creator and channel research. Rank creators and rising channels for a given search term, which is useful when you are building influencer lists for Chinese-speaking audiences.
- Comment and sentiment work. Pull viewer comments from the results you collect, then analyze tone and content performance.
- Video metadata collection. Gather titles, view counts, dates and tags at volume to support content strategy and market analysis.
All three start from a search URL and differ only in which fields you extract and how often you re-run the query.
Request flow, step by step
- Create an account to receive an API key and the free starting credits.
- Install the client for your stack — Python, Node, Go, PHP, Ruby or Java — or skip the SDK and use plain cURL. Each scrape becomes one function call or one GET request.
- Send a GET request containing your API key and a Bilibili search URL on bilibili.tv. JavaScript rendering and residential proxy rotation happen server-side, and rendered HTML comes back ready to parse.
- Add advanced parameters only when the page needs them:
render_jsfor JavaScript execution,stealth_proxyfor CAPTCHA-heavy targets,country_codefor geo-targeting, andai_extract_rulesfor natural-language extraction.
Field and control map
Use this to decide which request options you actually need before you send anything.
- Output shape. Default is rendered HTML. Add
extract_ruleswith CSS selectors mapped to field names, orai_extract_ruleswith a natural-language spec, to receive parsed JSON. - Rendering.
render_jsexecutes page JavaScript. It is the option that makes dynamic search listings readable. - Blocking.
stealth_proxyis the heavier anti-CAPTCHA path; rotating residential proxies are already part of the standard flow. - Geography.
country_coderoutes the request through a chosen country or territory. - Screenshots and selectors. Full-page screenshots and CSS/XPath extraction rules are available on every paid tier.
How request options change credit cost
Credits are consumed per successful request and the multiplier depends on which options you enable. The published rates are:
- Base request: 1 credit.
- JavaScript rendering enabled: 5 credits.
- Premium proxy with JavaScript rendering disabled: 10 credits.
- Premium proxy with JavaScript rendering enabled: 25 credits.
stealth_proxy: 75 credits.
Credits are valid for one month and do not roll over. A search page that needs rendering and a stealth proxy is therefore far more expensive per call than a plain rendered request, which is why it is worth testing whether the lighter option already returns the fields you need.
Telling failures apart
Three different problems look similar in a response, and each has a different fix:
- Empty or partial render. The page loaded but the listing did not populate. This usually means JavaScript did not finish; check that
render_jsis on and considerstealth_proxyif the page is being throttled. - Render succeeded, JSON is empty. The page had content but your selectors missed it. Re-check
extract_rulesagainst the rendered HTML, or switch toai_extract_ruleswith a plain-language description of the fields. - Content is behind a login. Post-login pages are out of scope. Only public-facing search results are addressable, and you should review the target site's terms of service before deploying.
Worked example: a creator-tracking run
Suppose you want to track rising creators for a search term. You send one GET request with the search URL, render_js enabled, and extract_rules mapping the creator handle and view count to field names. The response is JSON with one object per result. You store the handle and view count, then re-run the same request on a schedule and compare counts over time. If a later run returns an empty array while the HTML mode shows results, the selectors have drifted and need updating — that is a selector problem, not a blocking problem.
Plans and limits
The free starting allowance is 1,000 credits with no card required. Paid tiers scale credits and concurrent requests together, from a small hobby tier up through enterprise levels, and every paid tier includes JavaScript rendering, rotating and premium proxies, geotargeting, and screenshot/extraction rules. Priority email support, a dedicated account manager and team management appear only on the higher tiers. Prices exclude VAT. Check the current pricing page before committing, since plan details can change.
Compliance and data handling
Public-facing pages can generally be scraped, but the target site's terms of service govern what you may do, and post-login content should be avoided. The service does not collect or store personal data from scraped sites unless the user explicitly requests it. Proxy rotation and headless browser rendering are used to reduce IP-based blocking and mimic ordinary browsing behavior.
| Option combination | Credits per successful request |
|---|---|
| Base request | 1 |
| JavaScript rendering enabled | 5 |
| Premium proxy, JS rendering disabled | 10 |
| Premium proxy, JS rendering enabled | 25 |
| stealth_proxy | 75 |
Credits are valid for one month and do not roll over. Rates reflect the published schedule at the time of capture; confirm against the current pricing page.
| Tier | Monthly price | API credits | Concurrent requests | Priority support / account manager / team management |
|---|---|---|---|---|
| Hobby | $19 | 75,000 | 25 | Not included |
| Freelance | $49 | 250,000 | 50 | Not included |
| Startup | $99 | 1,000,000 | 100 | Not included |
| Business | $249 | 3,000,000 | 200 | Included |
| Business + | $599 | 8,000,000 | 400 | Included |
| Enterprise 14 | $999 | 14,000,000 | 500 | Included |
| Enterprise 24 | $1,599 | 24,000,000 | 600 | Included |
| Enterprise 41 | $2,399 | 41,000,000 | 700 | Included |
| Enterprise 69 | $3,599 | 69,000,000 | 800 | Included |
| Enterprise 120 | $5,799 | 120,000,000 | 900 | Included |
All prices exclude VAT. JavaScript rendering, rotating and premium proxies, geotargeting, and screenshot/extraction rules are included on every paid tier. Figures are a dated reference; verify current plans before purchase.
Frequently asked questions
Do I need an account to scrape Bilibili Search?
You do not need a Bilibili account. You do need an API key from the service, which comes with 1,000 free credits and no card requirement; send the search URL and the rendering and proxy work is handled for you.
Is scraping Bilibili Search legal?
Public-facing pages can usually be scraped, but the target site's terms of service should be reviewed before you deploy anything, and post-login content should be avoided.
What data can I extract from Bilibili Search?
Whatever the public page renders is fair game. For structured JSON, hand the request extract_rules with CSS selectors, or let ai_extract_rules interpret a plain-language description of the fields you want.
How do I get structured JSON from Bilibili Search?
Two routes lead to parsed JSON instead of raw markup. With extract_rules you pair each CSS selector with the field name it should fill; with ai_extract_rules you describe the desired fields in ordinary language and the extraction is handled for you.
Which programming languages can I use to scrape Bilibili Search?
Any. SDKs are published for Python, Node.js, Go, PHP, Ruby and Java, and plain cURL works too. Pick whatever your stack already uses.
How much does it cost to scrape Bilibili Search?
Signup includes 1,000 free credits with no card required. Paid plans start at $19/month for higher volume and concurrency. Per-request cost depends on options: 5 credits for JS rendering, 25 for premium_proxy with JS, 75 for stealth_proxy.
Should I request HTML or JSON?
Request JSON when you already know which fields you need and want the extraction done in the request. Request HTML when you want to parse the DOM yourself or reuse the same response for several different extractions.