Kuaishou hashtag_posts API
Kuaishou hashtag_posts data in one REST call — normalized to the stable JSON schema shared across every FetchPI platform.
- 1 documented endpoints
- GET /v1/kuaishou/hashtags/{tag}/posts
Contract summary (English): List the posts of a Kuaishou tag (capability kuaishou.hashtag_posts)
- Normalized response entity
- kuaishou/hashtag_posts
- capability
- kuaishou.hashtag_posts
Every response also carries freshness (cache / default / live) and billing metadata.
Use cases
- Monitor what a {{platform}} account publishes, in order, with normalized per-item metrics.
- Detect new activity when scheduled jobs re-query the feed — ideal for alerting and digest workflows.
- Benchmark publishing cadence and engagement across accounts with comparable, structured output.
Response fields
Kuaishou kuaishou.hashtag_posts response (normalized envelope)
Response envelope of the /v1/kuaishou kuaishou.hashtag_posts capability. Cursor is opaque and platform-independent; page size follows the request's `limit` parameter (1..100, default 20).
| Field | Type | Required | Description |
|---|---|---|---|
| data | post[] | Required | — |
| next_cursor | string | null | Required | Opaque pagination cursor; null when the list is exhausted. |
| meta.request_id | string | Required | — |
| meta.freshness.mode | cache | default | live | Required | — |
| meta.freshness.age_seconds | integer | null | Optional | — |
| meta.freshness.source_layer | cache | db | upstream | Required | — |
| meta.freshness.stale | boolean | Optional | — |
| meta.billing.cache_hit | boolean | Required | — |
| meta.billing.amount_credits | integer | Required | Credits actually charged for this request (the settlement unit; 1 credit = $0.0001, permanent). |
Field notes are shown in the contract's original English.
Response meta
| Field | Type | Required | Description |
|---|---|---|---|
| mode | cache | default | live | Required | Effective mode after merging param > max_age > source policy (D-004). |
| age_seconds | integer | null | Optional | Age of served data; null when unknown. |
| source_layer | cache | db | upstream | Required | Which layer served the response (PRD §10). |
| stale | boolean | Optional | True when stale data was served under stale_if_error / SWR (D-004). |
| billing.amount_credits | integer | Required | Micro-USD (1e-6 USD) actually charged for this request. |
| billing.cache_hit | boolean | Required | — |
Field notes are shown in the contract's original English.
Example request & response
/v1/kuaishou/hashtags/{tag}/postscurl -H "Authorization: Bearer $MESHDATA_API_KEY" \
"https://api.fetchpi.com/v1/kuaishou/hashtags/trending/posts"{
"data": [
{
"id": "5566778899001",
"platform": "kuaishou",
"type": "post",
"author": {
"id": "3185500122",
"username": "meshdata_ks",
"display_name": "MeshData 快手号",
"verified": false
},
"text": "快手短视频数据示例。",
"created_at": "2026-09-16T10:00:00Z",
"metrics": {
"likes": 8642,
"comments": 512,
"shares": 87,
"views": 154000
},
"attachments": [
{
"type": "video",
"preview_image_url": "https://cdn.example.com/cover/kuaishou-5566778899001.jpeg",
"duration_ms": 38400
}
],
"fetched_at": "2026-09-21T09:00:00Z"
}
],
"next_cursor": null,
"meta": {
"request_id": "req_01HTXQ8Z9HTQ",
"freshness": {
"mode": "default",
"age_seconds": 0,
"source_layer": "upstream",
"stale": false
},
"billing": {
"amount_credits": 200,
"cache_hit": false
}
}
}Free demo
Create a free account, grab an API key and call this endpoint from the browser-based Playground.
Try it in the PlaygroundParameter tables, error codes and response semantics for this endpoint live in the API documentation.
Open the endpoint referenceFrequently asked questions
Can I poll the feed on a schedule?
Yes — the endpoint is a plain REST call, so any scheduler can re-query it. Use the freshness parameters to control how current each answer is and how it is billed.
Can I try this endpoint for free?
Yes — register an account, grab an API key and call it from the Playground in the console.
How is the hashtag_posts capability billed?
Data API calls are billed per request in credits, with different cache/live freshness multipliers. Current per-capability prices live on the pricing page.
Pricing
Per-request credit billing with cache/live freshness options — current prices live on the pricing page.