Douyin Creator search API

POST

API health

24h health
Normal
24h average time
—
  • Healthy / normal
  • Available
  • Limited
  • Mostly down
Normal

Search Douyin creator accounts by nickname, handle or phrase, with follower count, gender, verification and live status, plus the secUid for follow-up calls. Narrow with follower_range and user_type; matches are candidates, not a confirmed identity.

Douyin Creator search finds accounts by keyword and returns each one's nickname, Douyin ID, profile link, avatar, follower count, gender, verification status and whether it is live right now. It is where creator campaigns, competitor mapping and influencer shortlists start: pass a result's user_id (the secUid) to follow-up capabilities; uid is the same account's numeric ID.

Narrow candidates by followers with follower_range and by account kind with user_type (general, business or verified individual). Results are candidates, not exact identity matches: accounts with the same or similar names can appear, so check the profile before you reach out. is_live reflects the moment of the call.

Price $0.56 per 1,000 requests ($0.000556 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

Paste this into your AI assistant. It already holds this endpoint's parameters, response fields and an example request, so the assistant can ask what you need and then write the scraper.

Please help me write a data collection script with the EveryInfra Douyin Creator search endpoint (douyin/creator_search).

Endpoint contract:
- 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 douyin and action to creator_search, and put the parameters inside params.
- Required parameters:
  - keyword: A creator nickname, Douyin ID, or related search phrase used for account discovery. It does not run the video search action or guarantee an exact identity match.
- Optional parameters:
  - follower_range: Filters creator_search by an account's follower-count band. Use under_1k, 1k_to_10k, 10k_to_100k, 100k_to_1m, or over_1m; omit it to leave the band unrestricted. (allowed: 100k_to_1m / 10k_to_100k / 1k_to_10k / over_1m / under_1k)
  - user_type: Filters creator_search by account category: general, business, or verified_individual. It is not a buyer category or proof of legal identity. (allowed: business / general / verified_individual)
  - limit: The most rows to return in this call, an integer from 1 to 20. The default applies when you leave it out, and a call can return fewer rows. Larger values return 422 before any charge. (default: 20)
- Returns a list of records. Main fields of each record: user_id, douyin_id (Douyin ID: the searchable ID the accoun…), nickname (Display name of the account), url, avatar_url, follower_count, gender (Gender as shown on the account), is_verified, verify_reason (Verification note as written (profile,…), is_live (Whether the account was live at the mom…), uid (Numeric user ID (profile / creator_sear…), source_keyword (The search term this row matched).
- Example request body:
{
  "platform": "douyin",
  "action": "creator_search",
  "params": {
    "keyword": "美食"
  }
}
- Price: $0.56 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

NameInTypeRequiredDefaultDescription
AuthorizationheaderstringYes-Bearer followed by your API key. Create it in the console; never put it in a URL or a code repository.
platformbodystringYesdouyinPlatform identifier, fixed value.
actionbodystringYescreator_searchCapability identifier, fixed value.
keywordbody.paramsNot declaredYes-A creator nickname, Douyin ID, or related search phrase used for account discovery. It does not run the video search action or guarantee an exact identity match.
follower_rangebody.paramsenumNo-Filters creator_search by an account's follower-count band. Use under_1k, 1k_to_10k, 10k_to_100k, 100k_to_1m, or over_1m; omit it to leave the band unrestricted.Allowed values100k_to_1m10k_to_100k1k_to_10kover_1munder_1k
user_typebody.paramsenumNo-Filters creator_search by account category: general, business, or verified_individual. It is not a buyer category or proof of legal identity.Allowed valuesbusinessgeneralverified_individual
limitbody.paramsinteger (1–20)No20The most rows to return in this call, an integer from 1 to 20. The default applies when you leave it out, and a call can return fewer rows. Larger values return 422 before any charge.

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": "douyin",
  "action": "creator_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

There is no real sample for these example parameters yet: this shows the response shape and fields from the contract, with … as placeholders. It is not the result of a real call.

json
{
  "id": "req_…",
  "platform": "douyin",
  "action": "creator_search",
  "results": [
    {
      "user_id": …,
      "douyin_id": …,
      "nickname": …,
      "url": …,
      "avatar_url": …,
      "follower_count": …,
      "gender": …,
      "is_verified": …,
      "verify_reason": …,
      "is_live": …,
      "uid": …,
      "source_keyword": …,
      "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.

FieldMeaning
user_idUser's unique ID on the platform.
douyin_idDouyin ID: the searchable ID the account holder chooses.
nicknameDisplay name of the account.
urlLink to the record on the platform.
avatar_urlAvatar image link. Some platforms return sized CDN links that can expire.
follower_countFollowers. null means not disclosed, not 0.
genderGender as shown on the account.
is_verifiedWhether the platform verified the account. null means it cannot be determined.
verify_reasonVerification note as written (profile, creator_search), for business or individual verification; empty or absent for unverified accounts.
is_liveWhether the account was live at the moment of the call; a point-in-time state.
uidNumeric user ID (profile / creator_search). user_id is the secUid; both identify the same account.
source_keywordThe search term this row matched.
platformSource platform identifier, the same as platform in the request (for example xiaohongshu, tiktok).

FAQ

Is every result the person I searched for?

Not necessarily. Creator search returns accounts related to the keyword, and accounts with the same or similar nicknames can appear. Before you rely on a match, open its url to check the profile, compare the douyin_id, and for verified accounts read verify_reason.

How do I find creators of the right size?

Set follower_range to under_1k, 1k_to_10k, 10k_to_100k, 100k_to_1m or over_1m to keep accounts in that band; leave it out for no limit. Add user_type to leave out business accounts or keep only verified individuals.

What can I look up once I have a creator?

Pass the user_id from a result to Douyin Posts by user, Creator audience and Creator growth trend to see what the account posts, who follows it and how fast it grows before you decide to work with it.

Errors and billing

401
Missing or invalid key. Authentication runs before parameter checks, so unauthenticated requests never see the parameter schema.
422
Wrong parameter name or value. The error lists the parameters and allowed values this capability accepts and the closest match; it happens before any charge.
402
Insufficient balance. Top up first.
429
The account's per-minute request limit was reached (all of its API keys count together; a key's own lower limit applies first). Wait for Retry-After and try again; a rate package in the console raises the limit.
503
Could not complete right now. Any charge for the call goes back to your balance automatically, and the billing receipt in the response states the actual outcome, including when it is not yet known. Do not resend blindly.
200 empty
The request completed without data and is not charged (billing.reason = empty_result_refunded).