Kuaishou Trending API

POST

API health

24h health: Normal
24h average time: —

Healthy / normal
Available
Limited
Mostly down

Normal

Last 24 hours

Last 30 days

Take Kuaishou's hot list in one call, up to 50 entries. Each entry has its rank (the pinned entry is first), title, heat value as a whole number, badge such as new or exclusive, cover image and, usually, the short IDs of the videos behind it. Those IDs work directly in video and comments. limit can only lower the count.

Price $0.81 per 1,000 requests ($0.000806 per call). Failed calls and empty results are not charged. Synchronous. For slow jobs add "mode": "async" to the body, take the job_id and poll.

AI prompt

Please help me write a data collection script with the EveryInfra Kuaishou Trending endpoint (kuaishou/trending).

How the endpoint works:
- Request: POST https://api.everyinfra.com/api/v1/social with the header Authorization: Bearer <API key>. Read the key from the EVERYINFRA_API_KEY environment variable and never hard-code it.
- In the request body, set platform to kuaishou and action to trending, and put the parameters inside params.
- No required parameters.
- Optional parameters:
  - limit: The most rows to return in this call, an integer from 1 to 50. The default applies when you leave it out, and a call can return fewer rows. Larger values are accepted and capped at the maximum. (default: 50)
- Returns a list of records. Main fields of each record: rank (Hot-list position from 1 (trending), in…), title, hot_value (Heat value shown on the hot list (trend…), label (Hot-list badge as shown (trending), suc…), cover_url (Cover image), video_ids (Short IDs (starting with 3x) of the vid…).
- Example request body:
{
  "platform": "kuaishou",
  "action": "trending",
  "params": {}
}
- Price: $0.81 per 1,000 requests; failed and empty results are not charged.
- For dozens or hundreds of targets, add "mode": "async" to the body: you get a job_id at once and poll GET https://api.everyinfra.com/api/v1/jobs/{job_id} for the result.
- On 422, fix the request using the suggested parameter names and allowed values in the error; on 429 or 503, wait for Retry-After and try again.

Before writing code, ask me which targets I need, how many, which fields, and what output format I want; then confirm the plan and the rough cost with me.

Request parameters

Name	In	Type	Required	Default	Description
`Authorization`	header	`string`	Yes	-	Bearer followed by your API key. Create it in the console; never put it in a URL or a code repository.
`platform`	body	`string`	Yes	`kuaishou`	Platform identifier, fixed value.
`action`	body	`string`	Yes	`trending`	Capability identifier, fixed value.
`limit`	body.params	`integer (1–50)`	No	`50`	The most rows to return in this call, an integer from 1 to 50. The default applies when you leave it out, and a call can return fewer rows. Larger values are accepted and capped at the maximum.

Code samples

bash

curl -X POST 'https://api.everyinfra.com/api/v1/social' \
  -H "Authorization: Bearer $EVERYINFRA_API_KEY" \
  -H 'Content-Type: application/json' \
  --data-raw '{
  "platform": "kuaishou",
  "action": "trending",
  "params": {}
}'

OpenAPI definition (JSON)Samples read the key from the EVERYINFRA_API_KEY environment variable; copied code never contains your key.

Response example

Field preview

No sample response is available for these parameters yet. This preview shows the response shape and fields from the API definition, with … as placeholders; it is not the result of a live call.

json

{
  "id": "req_…",
  "platform": "kuaishou",
  "action": "trending",
  "results": [
    {
      "rank": …,
      "title": …,
      "hot_value": …,
      "label": …,
      "cover_url": …,
      "video_ids": …,
      "platform": …
    }
  ],
  "count": …,
  "billing": {
    "charged": …,
    "charged_usd": …,
    "balance_after_usd": …,
    …
  },
  "quota": { … }
}

Response fields

Business data is in results. The table lists the fields a record can contain; values the platform does not show are never made up.

Field	Meaning
`rank`	Hot-list position from 1 (trending), in Kuaishou's order; the pinned entry is first.
`title`	Title. null when the platform has no titles (for example text-only posts).
`hot_value`	Heat value shown on the hot list (trending), converted from text such as 12.442 million to the whole number 12442000; the pinned entry may have none. Compare it only within the list.
`label`	Hot-list badge as shown (trending), such as pinned, new or exclusive; absent when there is no badge.
`cover_url`	Cover image; on trending, the picture for the hot-list entry.
`video_ids`	Short IDs (starting with 3x) of the videos behind a hot-list entry (trending); pass one as `url` to video or comments. Sometimes the list carries no video IDs, and the field is then absent.
`platform`	Source platform identifier, the same as platform in the request (for example xiaohongshu, tiktok).

Errors and billing

401: Missing or invalid key.
402: Insufficient balance. Top up first.
422: Invalid parameter name or value. Fix it using the suggestions in the error. No charge.
429: Per-minute request limit reached. Wait for Retry-After, then try again.
503: Could not complete. The held charge is returned to your balance. If the outcome is unknown, verify it before you retry.
200 empty: No data. No charge.

Errors