Kuaishou Public Data API | SandBase
Read public Kuaishou hot list, search, shopping rankings, and videos with one REST API. No Kuaishou login, no SDK — one SandBase key, built for agents.

Kuaishou is a Chinese short-video platform with creator and commerce features — a hot list, comprehensive search, shopping rankings, and video streams that map directly onto trend research, e-commerce monitoring, and content analytics. Getting at it programmatically usually means reverse-engineering the app, rotating tokens, and rebuilding a scraper every time the app changes.
The SandBase Kuaishou public data API removes that setup tax. It reads the public Kuaishou hot list, search results, shopping rankings, and videos through plain REST endpoints — one SandBase API key, no Kuaishou login and no SDK. The endpoint API reference is the source of truth for each parameter and for the response envelope (id/status/model/outputs[0].data); the business-payload field names shown below are an illustrative shape, not a guaranteed schema, so confirm them against a live response.
This is not Kuaishou’s official open platform. Use Kuaishou’s official channels when you need authenticated member actions or a licensed data agreement. Use SandBase when your workflow needs public, read-only data for research and monitoring. Ready to try it? Get a SandBase API key and browse the Kuaishou endpoints.
Key takeaway
- One API reads the public Kuaishou hot list, search results, shopping rankings, videos, and comments.
- The Model API endpoints in this guide are called with
POST /v1/api/kuaishou/<path>— pass only that endpoint’s params, no SDK, oneSANDBASE_API_KEY.- Endpoints key off natural identifiers: a
keywordfor search, aphoto_idfor a video, or auser_idfor a creator.- It returns public, read-only data only. There is no posting, no platform login or OAuth on your side, and no private data; authenticate with a SandBase API key.
Current scope: search candidates or read one profile
This 2026-11-08 repair checks free inspect and public references for user search V2 and single user V2. It makes no business API call. The broader hot-list, shopping, video and comment descriptions remain historical navigation from the original 2026-09-27 hub, not fresh execution tests.
Choose a keyword search page when you need candidates; choose a profile directly when you already know its numeric user_id. The creator research tutorial supplies one checked Python request and separates existing-key, connected-agent and new-project setup. It does not automatically select a candidate, fetch every profile or read their posts.
Both selected endpoints currently list $0.01 and eligibility for an organization’s shared 100-call daily quota across eligible APIs, resetting at 00:00 UTC. Eligibility is not remaining allowance. This repair did not inspect a balance or claim free success; two separately chosen requests list at $0.02 before quota effects.
The original cover is retained conceptual artwork. Names, counts, cards or rankings pictured in it are not a new response, measured performance or verified customer data.
Which Kuaishou API do you need?
| Your need | Choose | Why |
|---|---|---|
| Post, act as a member, or use account-authorized data | Kuaishou’s official channels | Member and account operations run through Kuaishou directly. |
| Read the public hot list, search, shopping rankings, or videos | SandBase Kuaishou public-data API | Plain REST, one SandBase key, structured JSON for read-only workflows. |
| Private or account-only data | Neither public workflow | That data is out of scope for this public-data guide. |
What you can get from the Kuaishou API
The catalog spans an app surface and a web surface. Grouped by job:
- Hot list & rankings — the trending hot list and shopping top list.
- Search — comprehensive, live, and tag search by keyword.
- Videos — a single video and its comments by
photo_id. - Creators — public creator reads by
user_id.
Check each endpoint’s live API reference for the exact surface and parameters before you build; availability differs by endpoint.
Historical Kuaishou catalog view, not a current endpoint-count or quota measurement. The From $0.001 brand-list label does not price the selected $0.01 creator routes.
What Kuaishou provides vs. what SandBase adds
Public data comes from Kuaishou. SandBase supplies a shared authenticated API entry point; it does not own Kuaishou or make every endpoint’s business response interchangeable. Check parameters, business status, payload structure, availability and budget for each selected route. A successful search does not validate a profile or a video request.
Quick start: one search page
Configure SANDBASE_API_KEY locally, then send a keyword and an empty pcursor. The command has time limits and no redirect or retry option. It prints the response; it does not perform the Python tutorial’s business validation.
curl --fail-with-body --connect-timeout 10 --max-time 90 \
-X POST https://api.sandbase.ai/v1/api/kuaishou/app/search-user-v2 \
-H "Authorization: Bearer $SANDBASE_API_KEY" \
-H "Content-Type: application/json" \
-d '{"keyword":"人工智能","pcursor":""}'Check completed status and the object at outputs[0].data, then integer responseCode 0 and a mixFeeds array whose entries contain user objects. For the independent profile task, use /v1/api/kuaishou/app/one-user-v2 with only {"user_id":"3795214411"}; check integer result 1, userProfile.profile and userProfile.ownerCount objects. Do not run both as a hidden setup step. The known ID is the public schema example, not a newly executed request.
Already connected agents should reuse their existing credential configuration. New agents can read SKILL.md, quickstart.md and the human quickstart. Supply a task and keyword or known ID; never paste the key into the prompt. Request one checked result with missing fields called out before allowing a larger workflow.
Retained historical hot-list illustration
The following JSON is the original hub’s illustrative hot-list shape, not a new run or the search/profile contract. Its list-shaped business data must not be copied into either selected route’s parser. The old Python is preserved in the historical archive, not recommended as the current quickstart.
{
"id": "0e6f9926-eb40-4d04-94bf-35b070748803",
"status": "completed",
"model": "kuaishou/web/hot-list-v1",
"outputs": [
{
"data": [
{ "rank": 0, "name": "…", "tagType": "…", "viewCount": null }
]
}
]
}An incomplete or failed run stops field access. Do not assume an error response has no outputs, expose its raw diagnostic body or treat a missing payload as an empty result.
Historical hot-list reference, retained for the archived example; it does not validate the current search or profile request. Its old model-body example and empty-data placeholder are not the current request or a business result.
Capability map
Historical catalog navigation from 2026-09-27; the following routes and parameters were not revalidated in this repair.
| Capability cluster | Representative endpoint | Typical use |
|---|---|---|
| Hot list | kuaishou/web/hot-list-v1 | Trending-topic monitoring |
| Shopping ranking | kuaishou/app/shopping-top-list | Live-commerce and product tracking |
| Search | kuaishou/app/search-comprehensive | Keyword content discovery |
| Video | kuaishou/web/one-video-v2 | Read a video by photo_id |
| Video comments | kuaishou/app/video-comment | Engagement and sentiment inputs |
Paging differs by endpoint — several endpoints return or accept a cursor value such as pcursor. Read each endpoint’s schema.
Historical shopping-top-list reference showing subTabId/subTabName parameters. Shopping behavior is not revalidated; the old model-body example and empty-data placeholder are not current instructions.
Before adding another request
A search result is a candidate, not an instruction to fetch that account automatically. Review its explicit identity fields and your research purpose first. The original creator tutorial’s pattern made one search plus up to five profile calls, up to six requests; a shared envelope did not make that one transaction.
Search uses pcursor, and the saved reference also contains a separate recoPcursor. These are not interchangeable. This repair uses only the first page and does not test continuation or stopping rules. Do not increment a cursor, follow a guessed token or decode tracking strings to reconstruct an absent user_id. Further video, comment or shopping requests need their own current reference and budget.
Historical capability navigation
The original hub grouped hot-list, shopping and comprehensive search into these research use cases. They are possible next tasks, not additional steps validated by this repair. Check the selected route’s current inputs, response structure, access and budget before using it.
| Historical capability | Potential research question | Before a new request |
|---|---|---|
kuaishou/web/hot-list-v1 | Which topics appear in a hot-list sample? | Verify the current request and item schema; a snapshot does not establish a trend. |
kuaishou/app/shopping-top-list | What entries appear in a shopping ranking? | Verify its category/input options; a ranking is not a verified sales report. |
kuaishou/app/search-comprehensive | What content matches a topic? | Verify its own fields and continuation contract; do not reuse user-search rules. |
No polling schedule, shopping call or comprehensive-search continuation is executed or provided as runnable code here.
Keep the record’s meaning when building a report
The selected profile reference places the account record under userProfile.profile and counters under userProfile.ownerCount. authorInfo contains flags; it is not a substitute profile. Top-level totalPhotoLike can contain links and entrance UI metadata, while ownerCount.total_photo_like is the observed numeric counter. Do not rank accounts by the link object or silently replace missing values with zero.
The short profile README JSON is clipped before userProfile, but the full saved example dated 2026-10-07 contains it. Clipped documentation and a missing field in a complete response are different evidence. Neither this saved example nor the original September experiments is a November business execution. The tutorial preserves dated trimmed fragments and explains the current validation boundaries.
Keep unknown, zero and false distinct. Search fansCount and profile ownerCount.fan can come from different requests and times; record provenance before comparing them. Cumulative likes do not establish recent engagement, and a keyword sample cannot establish a whole niche’s market share. Avoid presenting a partially populated profile as a complete audience assessment.
A photo_private counter is not permission to read private posts. Shop entrance links and product counts do not prove sales or conversion, and an IP-location label is not a precise person-location measurement. No link visiting, avatar download, video collection or model analysis happens automatically in the current tutorial. Decide which missing question warrants another request after you inspect the first record.
For operational errors, keep the layers separate: HTTP status, SandBase completion and selected provider status. Stop on authorization, budget or rate errors and review the cause. A timeout can leave the outcome uncertain; an automatic retry may create an additional call. Error reports should identify the failing layer without printing keys, raw headers or diagnostic response bodies. Local mock tests can check that handling but cannot establish live availability.
Limitations and boundaries
- Public, read-only data only. No posting, following, or private/account-only data.
- Rate and volume. Treat responses as best-effort reads; stop on errors and inspect the cause before explicitly choosing another request.
- Parameters and shapes follow the upstream surface. Identifiers vary (
keyword,photo_id,user_id); paging is a per-endpoint cursor such aspcursor. Inspect a real response and read the schema first. - Verify endpoints against the live reference. Availability and fields can change; confirm before building on a specific endpoint.
- This is not an official Kuaishou partnership. SandBase provides uniform access to public data; respect Kuaishou’s terms and applicable rules for your use case.
FAQ
Do I need a Kuaishou developer app or login?
No. You authenticate to SandBase with your SANDBASE_API_KEY. These read endpoints do not require a Kuaishou account or OAuth on your side.
What identifies a video or creator?
A photo_id for a video and a user_id for a creator. Search takes a keyword.
How does pagination work? For the selected search, the schema names pcursor and describes an empty first-page value. The saved response also has recoPcursor, a different field. Continuation is not tested here; consult the exact route before implementing it.
Can I read private or account-only data? No. The API returns public data only. Private and account-authorized content are out of scope.
Start with one bounded task
Reuse your existing key or follow the setup guide, choose a keyword page or a known profile, and inspect one checked response. Continue with the creator tutorial, user search reference or single-user reference. The broader catalog is navigation for a separately verified next task.
Found this useful? Share it