Kuaishou API
8 endpoints read Kuaishou: videos, users, comments, trends. From $0.0020 a call. No Kuaishou login and no cookie; a failed call is free.
One call, as it came back
A recorded call, fields already tidied up: ready for an AI or a spreadsheet.The first 7 rows of a response recorded 2026-10-12 18:52 UTC.
Run it in the Playground · $0.0200{
"code": "ok",
"request_id": "a19f2e0b-62a1-4300-9571-2f2b2807ce2b",
"data": {
"items": [
{
"id": "3xegr2ov53lfrqs",
"url": "https://www.kuaishou.com/short-video/3xegr2ov53lfrqs",
"text": "露营装备这件事，越简单越好",
"published_at": "2026-10-10T23:04:11.943Z",
"author": {
"id": "3x1eyjiwkiajmm",
"username": null,
"name": "小林的周末",
"avatar_url": "https://p2.a.yximgs.com/uhead/AB/2026/09/15/3500e4210a201dc1eadc48dd.jpg",
"verified": false
},
"metrics": {
"likes": 0,
"comments": 0,
"shares": 0,
"favorites": 0,
"views": 4
}
},
// … 9 more
]
},
"page": {
"next_cursor": "c1.6X2ZXQ7PYzJDBBMdubcMGSp6sl73SlvbUvsoO4Er",
"cursor_expires_at": "2026-10-12T19:52:39.000Z",
"has_more": true,
"returned": 10
},
"warnings": [],
"meta": {
"capability": "kuaishou.videos.search",
"result_status": "complete",
"fetched_at": "2026-10-12T18:52:39.000Z",
"cached": false,
"replayed": false,
"unavailable": {
"type": "capability",
"title": "platform",
"lang": "capability",
"author.followers": "capability",
"metrics.reposts": "capability",
"images": "capability",
"hashtags": "capability",
"mentions": "capability",
"is_pinned": "capability",
"post_id": "platform",
"parent_id": "platform",
"root_id": "platform"
},
"billing": {
"amount": "0.02",
"currency": "USD",
"balance_after": "9.98"
}
}
}From a response recorded 2026-10-12 18:52 UTC. Names, text and IDs are examples, and so are the links: none is the recorded one (the page shows no one's personal data); the figures are as recorded. Long lists are cut. The request ID, cursor and balance are made up.
What you can get
Each row is an endpoint: what it returns and what one call costs.
What people build with it
Ready-made tasks your AI can run on Kuaishou data. Each is a few calls under a spending cap.
Comments and word of mouth
“What are people praising and complaining about under this post?”
Competitor account monitoring
“What did competitors post this week, and which post took off?”
Keyword search and mentions
“What is being said about this brand or keyword on each platform?”
Ask about Kuaishou right inside Claude or Cursor
Add the DataXAPI MCP server and the AI finds the Kuaishou endpoint it needs and calls it; answers link back to the source. You pay for the calls it makes.
https://api.dataxapi.com/mcpStart in three steps
The call shown here is Kuaishou video search. Every other Kuaishou endpoint is called the same way and answers in the same envelope.
Get a key
Sign in with an emailed code or Google. Free trial, no card needed.
Call it, or let your AI call it
One GET from your code. Or paste this prompt into your agent with your key in it: it sets itself up, then finds and calls these endpoints by itself.
Read the same shape every time
Items are in data.items (one object in data.item), the next page in page.next_cursor, the charge in meta.billing.amount. A failed call is not charged.
curl -G "https://api.dataxapi.com/v1/kuaishou/videos/search" \ --data-urlencode "query=露营装备" \ -H "Authorization: Bearer $DATAXAPI_API_KEY"
from dataxapi import DataXAPI dx = DataXAPI() # reads DATAXAPI_API_KEY result = dx.kuaishou.videos.search(query="露营装备") print(result["data"]["items"])
import { DataXAPI } from "@dataxapi/sdk";
const dx = new DataXAPI(); // reads DATAXAPI_API_KEY
const result = await dx.kuaishou.videos.search({ query: "露营装备" });
console.log(result.data.items);dataxapi call kuaishou.videos.search 'query=露营装备'{
"mcpServers": {
"dataxapi": {
"type": "http",
"url": "https://api.dataxapi.com/mcp",
"headers": {
"Authorization": "Bearer ${DATAXAPI_API_KEY}"
}
}
}
}Add this to your MCP client, then ask your agent to call kuaishou.videos.search.
Edge cases
What the Kuaishou endpoints do at their edges, and what to check when a call does not return what you expected.
- Page sizes
- A list returns 10 to 60 items a page, depending on the endpoint. 5 of the 6 lists go on to a next page:
page.next_cursor, passed back ascursor, each page a call of its own. The others return one page only. - Fields it cannot give
- 7 of the 8 endpoints cannot fill every field of the object they return. Each endpoint's page lists which, and every answer repeats them in
meta.unavailable: a missing field is never a silent zero. - A missing object that reads as empty
- Kuaishou comment replies, Kuaishou user videos, Kuaishou video comments: an object that does not exist cannot be told from one with nothing under it, so the answer is an empty result, not a 404, and is charged as an empty result is.
- Snapshots
- Kuaishou hot list: a board is a snapshot refreshed every 10 minutes, and
meta.fetched_atsays when it was taken. - The video ID starts with 3x
- A video is named by the part of its web link that starts with 3x (kuaishou.com/short-video/3x…). Detail, comments and replies all take it.
- The user ID is digits
- Profiles and an account's videos take the numeric user ID, not the handle the user chose (快手号).
- Replies need two IDs
- Replies take the comment's ID and the 3x ID of its video. A reply does not name the comment it hangs under, and a comment does not say how many replies it has.
- Empty is not “not found”
- Comments of a video that does not exist, videos of a user that does not exist and replies to a comment that does not exist all come back as an empty list, charged as an empty result.
- Most popular first is priced apart
- An account's videos with
sort=popularhave a price of their own, and do not always come with a save count: where it is missing the field is null.
Questions about the Kuaishou API
Short answers. The details are on each endpoint's page.
How is the Kuaishou API priced?
Per call, no subscription. From $0.0020 to $0.0200 a call; each endpoint's page shows its own price. You are charged when data comes back; a failed call costs nothing.
Do I need a Kuaishou account or a cookie?
No. One DataXAPI key is all you hold: no Kuaishou login, no cookie, no device to keep alive. The endpoints return publicly visible data only.
Is the data live?
A call fetches from Kuaishou at that moment, and meta.fetched_at says when. Kuaishou hot list: a board is a snapshot refreshed every 10 minutes. A result is kept for 24 hours, so a retry with the same Idempotency-Key is not charged again.
Is an empty result charged?
A list that comes back empty is charged its price: the search was run. Reading one object that does not exist answers not_found and is free.
What happens when Kuaishou changes something?
A call that fails is not charged, whatever the reason. An endpoint that is paused answers capability_paused, also free, and GET /v1/catalog/status says what is up right now.
Related
Call Kuaishou with one key.
Free trial on sign-up: up to 50 calls at $0.0020. No card. No Kuaishou login, no cookie, no subscription. A failed call is free.