Search Kol Advanced V2

Search for Kol Advanced V2 with the Douyin API. The request takes a keyword. Use it to surface relevant records in a search or discovery tool. The GET request schema also lists followerRange, contentTag. Use the data to compare content across accounts or review audience feedback by video.

Selected price
$0.02 / callPublished pricing
Sellers / implementations
1 / 1
Requests · 30d
—Loading...
Success rate · 30d
—Loading...

Run sends a real API request. Charges follow the published API contract.

Request parameters
关键词/Keyword
Optional parameters (27)
粉丝范围(可选)/Follower Range (optional), 例如 10-100 表示10万-100万粉丝
内容标签(可选)/Content Tag (optional), 例如 tag-1 或 tag_level_two-7
页码(可选)/Page (optional)
排序方式(可选)/Sort order (optional)
搜索类型(可选)/Search type (optional)
营销目标(可选)/Marketing target (optional)
所属行业(可选)/Industry (optional)
是否明星(可选)/Whether superstar (optional)
报价类型(可选)/KOL price type (optional)
报价区间(可选)/KOL price range (optional)
内容主题(可选)/Content theme (optional)
人设标签(可选)/Persona tag (optional)
达人性别(可选)/Author gender (optional)
达人地域(可选)/Author location (optional)
内容调性标签(可选)/Tonality tag (optional)
连接人数区间(可选)/Connected user range (optional)
观众画像筛选(可选)/Audience image (optional)
粉丝画像筛选(可选)/Fans image (optional)
预期播放区间(可选)/Expected play range (optional)
预期CPM区间(可选)/Expected CPM range (optional)
预期CPE区间(可选)/Expected CPE range (optional)
互动率区间(可选)/Interaction rate range (optional)
完播率区间(可选)/Completion rate range (optional)
爆款率区间(可选)/Viral rate range (optional)
在途任务数区间(可选)/In-progress task range (optional)
是否精选达人(可选)/Whether curated author (optional)
指定达人列表(可选)/Specific author list (optional)

Sample response

{
  "cache_message": "This response is cached and accessible via the URL below for 24 hours at no extra cost. The cache is for request tracing only — it doesn't affect the API's data freshness and won't be returned through the API again.",
  "cache_message_zh": "本次响应已缓存,可通过下方 URL 直接查看,有效期 24 小时,访问缓存链接无额外费用。缓存仅用于请求溯源,不影响接口数据的时效性,也不会再次通过接口返回。",
  "cache_url": "<cache_url>",
  "code": 200,
  "data": null,
  "docs": "<docs>",
  "message": "Request successful. This request will incur a charge.",
  "message_zh": "请求成功,本次请求将被计费。",
  "params": {},
  "request_id": "<request_id>",
  "router": "",
  "support": "Discord: https://discord.gg/aMEAS8Xsvz",
  "time": "<time>",
  "time_stamp": 0,
  "time_zone": "America/Los_Angeles"
}

Response result

Response structure

Inferred from examples
  • cache_messagestring
  • cache_message_zhstring
  • cache_urlstring
  • codeinteger
  • datanull
  • docsstring
  • messagestring
  • message_zhstring
  • paramsobject
  • request_idstring
  • routerstring
  • supportstring
  • timestring
  • time_stampinteger
  • time_zonestring

Common questions

Do I need a separate key for every provider?

Use your OpenAny API key for standard API access. Read it from OPENANY_API_KEY in your environment and keep it out of prompts, source code and logs.

Are these providers interchangeable?

No. Each offering has its own inputs, pricing and response contract. Selecting a catalog offering does not establish automatic routing or fallback. Confirm the service contract before calling.

How is this API billed?

API-key calls use your shared balance at the selected implementation's published rate. Check the billing unit and request-specific pricing rules before making a paid call. Recorded usage determines the final charge under that contract.

Where do the price and contract come from?

The selected implementation publishes its provider, request contract, revision and billing rules through OpenAny's public API catalog. A revision number identifies a contract version, not a price update date. A price update timestamp is not supplied; do not treat a page date as one.

How do OpenAny Balance and x402 differ?

OpenAny Balance uses an API key and one shared balance. Card, USDC and x402 top-ups, card auto top-up and USDC subscriptions fund that balance; available routes appear on the Credits page. Direct x402 is a separate pay-per-request flow, available only on listings that show it and requiring an authorized payment client.

Does Playground send a paid request?

Yes. After you sign in, Run sends a real API request using an active OpenAny API key. Charges follow the published API contract and use your shared balance. Selecting an implementation, editing inputs and viewing sample responses do not send requests.

Use Search Kol Advanced V2 with your agent

Inspect endpoint contracts and confirm availability and pricing before a paid call.