Social data API · integration guide
Weibo API: keyword search, posts, comments and trends
Use the Weibo data API for public topic discovery and content retrieval. Search, post, comment, profile, user-post and trending capabilities are listed separately so you can choose the smallest set of calls needed for a research question.
Start from a question and a search mode
Search parameters can select different result types or ordering. Use only values shown in the reference; omitting an optional parameter is different from sending a guessed value. Select relevant posts before fetching their comment threads.
Treat trends as a time-specific snapshot
Capture the retrieval time with a trending response. A trending list is not a measurement of all platform activity and does not establish population sentiment. Compare like-for-like snapshots if you build your own trend history.
Separate post IDs from author IDs
Post detail and comment endpoints identify a post; profile and user-post endpoints identify an account. Retain original identifiers and source URLs. Do not convert long IDs through a JavaScript floating-point number.
Respond to errors without a retry storm
A 400 means the request or resource needs review, not necessarily an authentication problem. A 429 requires backing off. Empty or failed retrievals are not successful-call charges. Keep retries bounded and show a partial-data state to your users.
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/weibo/search | $0.002 |
| Post details | GET /v1/social/weibo/post | $0.002 |
| Profiles | GET /v1/social/weibo/user | $0.002 |
| Comments | GET /v1/social/weibo/comments | $0.002 |
| User posts | GET /v1/social/weibo/user-posts | $0.002 |
| Trending | GET /v1/social/weibo/trending | $0.003 |
Request example
curl --fail-with-body --get "https://api.chinaapi.ai/v1/social/weibo/search" \
-H "Authorization: Bearer $CHINAAPI_API_KEY" \
--data-urlencode 'query=NVIDIA'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.