Kuaishou Account search API

POST

API health

24h health: Normal
24h average time: —

Healthy / normal
Available
Limited
Mostly down

Normal

Last 24 hours

Last 30 days

Find Kuaishou accounts by nickname, handle or topic keyword, 20 per page. Each account has numeric user ID, nickname, Kuaishou handle when set, bio, gender, verification, follower and video counts and avatar. Pass the user_id to user_live, and page on with next_page_token.

Price $8 per 1,000 requests ($0.008 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 Account search endpoint (kuaishou/user_search).

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_search, and put the parameters inside params.
- Required parameters:
- keyword: Account search term: a nickname, a Kuaishou handle or a topic such as food. Returns matching accounts with follower and video counts.
- Optional parameters:
- page_token: Page token for comments and user_search. Leave it out for the first page, then pass back the previous response's next_page_token exactly as received, with the other parameters unchanged. Each page is one call.
- Returns a list of records. Main fields of each record: next_page_token (Page token (comments, user_search): pas…), user_id (Numeric Kuaishou user ID (rank actions,…), nickname, kwai_id (The account's Kuaishou handle (user_sea…), bio, gender (Gender on user_search: M or F), verified (Whether the account is verified (user_s…), follower_count, video_count, avatar_url.
- Example request body:
{
"platform": "kuaishou",
"action": "user_search",
"params": {
"keyword": "美食"
}
}
- Price: $8 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_search`	Capability identifier, fixed value.
`keyword`	body.params	`string`	Yes	-	Account search term: a nickname, a Kuaishou handle or a topic such as `food`. Returns matching accounts with follower and video counts.
`page_token`	body.params	`string`	No	-	Page token for `comments` and `user_search`. Leave it out for the first page, then pass back the previous response's `next_page_token` exactly as received, with the other parameters unchanged. Each page is one call; the last page has no `next_page_token`.

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_search",
  "params": {
    "keyword": "美食"
  }
}'

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_search",
  "results": [
    {
      "next_page_token": …,
      "user_id": …,
      "nickname": …,
      "kwai_id": …,
      "bio": …,
      "gender": …,
      "verified": …,
      "follower_count": …,
      "video_count": …,
      "avatar_url": …,
      "platform": …
    }
  ],
  "next_page_token": …,
  "pagination": { … },
  "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
`next_page_token`	Page token (comments, user_search): pass it back unchanged as page_token for the next page. Every row of a page carries the same value, which also appears at the top level of the response; absent on the last page.
`user_id`	Numeric Kuaishou user ID (rank actions, user_search, user_live); pass it to user_live.
`nickname`	Keeps the platform's own meaning
`kwai_id`	The account's Kuaishou handle (user_search); absent when the account has not set one.
`bio`	Profile bio written by the account; may contain line breaks and emoji.
`gender`	Gender on user_search: M or F.
`verified`	Whether the account is verified (user_search).
`follower_count`	Followers. null means not disclosed, not 0.
`video_count`	Keeps the platform's own meaning
`avatar_url`	Avatar image link. Some platforms return sized CDN links that can expire.
`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