Social data API · integration guide
Bilibili API: search videos and retrieve public discussion
Retrieve available Bilibili search results, video details, comments and public profile or trending data through one ChinaAPI key. Check the capability table for the exact identifiers and price before choosing a workflow.
Build a topic research workflow
Search for a topic, retain the returned video identifiers and retrieve details only for the videos relevant to your question. Pass the selected results to your own analysis model with source URLs and retrieval dates.
Keep Bilibili identifiers in their original form
A BV identifier, numeric video ID and user ID are different identifiers. Use the parameter named by the endpoint, and keep large numeric identifiers as strings in your application. Do not substitute a profile ID for a video ID.
Budget the research before expanding it
One search followed by several detail or comment requests is several billable calls. Read the prices below, cap the number of selected videos and pages, and stop on empty results instead of repeatedly submitting the same request.
Use summaries with traceable sources
Preserve the video URL and collection time alongside each result. Ask your model to distinguish observed content from its interpretation. Search ordering and available comments can change; a saved response is a snapshot, not a permanent ranking.
Available endpoints and USD prices
Per successful synchronous call. First top-up required. Captured 2026-10-29T17:56:18Z from the public catalog.
| Capability | Endpoint | USD / call |
|---|---|---|
| Search posts | GET /v1/social/bilibili/search | $0.002 |
| Post details | GET /v1/social/bilibili/post | $0.002 |
| Profiles | GET /v1/social/bilibili/user | $0.002 |
| Comments | GET /v1/social/bilibili/comments | $0.002 |
| User posts | GET /v1/social/bilibili/user-posts | $0.002 |
| Trending | GET /v1/social/bilibili/trending | $0.002 |
Request example
curl --fail-with-body --get "https://api.chinaapi.ai/v1/social/bilibili/search" \
-H "Authorization: Bearer $CHINAAPI_API_KEY" \
--data-urlencode 'keyword=火影忍者' \
--data-urlencode 'order=totalrank' \
--data-urlencode 'page=1' \
--data-urlencode 'page_size=42'Keep the key server-side. Replace resource identifiers with the content you intend to retrieve.
Billing and limits
Beta: paid accounts only. Complete your first top-up before calling this API. Trial credits cannot be used for social-data requests. This beta has no SLA and platform coverage may change.
You must comply with each platform's terms and applicable data rules. Do not use this API to build personal profiles. Login, contact extraction, engagement manipulation, and private or paid-content access are outside this beta.
Calls use your existing ChinaAPI key and balance. Synchronous calls charge only for HTTP 200 with data. Async POST creation reserves the price; failed or empty tasks are refunded, and GET task reads are free. Empty or failed results are not charged. A daily beta budget may return HTTP 429; retry after the UTC day resets. Repeating a successful synchronous request creates another billable call. Retry async creation with the same Idempotency-Key to avoid duplicate submissions.
Every successful page is separately billed. Prices and parameters can change; check the reference before deployment.