Kuaishou User live API

POST

API health

24h health: Normal
24h average time: —

Healthy / normal
Available
Limited
Mostly down

Normal

Last 24 hours

Last 30 days

Check whether a Kuaishou account is live right now from its numeric user_id, such as one from live_rank or user_search. You get is_live and the account's video count. It does not return the stream itself or past streams.

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 User live endpoint (kuaishou/user_live).

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 user_live, and put the parameters inside params.
- Required parameters:
  - user_id: Numeric Kuaishou user ID, such as 501353480, from the user_id of a live_rank or user_search row; a kuaishou.com/profile/<numeric ID> link is accepted too.
- Returns one object. Main fields: user_id (Numeric Kuaishou user ID (rank actions,…), is_live (Whether the account is live right now (…), video_count.
- Example request body:
{
  "platform": "kuaishou",
  "action": "user_live",
  "params": {
    "user_id": "2542916559"
  }
}
- 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	`user_live`	Capability identifier, fixed value.
`user_id`	body.params	`string`	Yes	-	Numeric Kuaishou user ID, such as `501353480`, from the `user_id` of a `live_rank` or `user_search` row; a kuaishou.com/profile/<numeric ID> link is accepted too.

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": "user_live",
  "params": {
    "user_id": "2542916559"
  }
}'

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": "user_live",
  "results": {
    "user_id": …,
    "is_live": …,
    "video_count": …,
    "platform": …
  },
  "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
`user_id`	Numeric Kuaishou user ID (rank actions, user_search, user_live); pass it to user_live.
`is_live`	Whether the account is live right now (user_live).
`video_count`	Keeps the platform's own meaning
`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