# 高级搜索kol V2/Search Kol Advanced V2

## OpenAPI Specification

```yaml
openapi: 3.0.1
info:
  title: ''
  description: ''
  version: 1.0.0
paths:
  /api/v1/douyin/xingtu/search_kol_v2:
    get:
      summary: 高级搜索kol V2/Search Kol Advanced V2
      deprecated: false
      description: >-
        # [中文]

        ### 用途:

        - 高级搜索kol V2，支持粉丝范围和内容标签筛选

        - 该接口数据使用企业账号进行请求，收费较贵。

        - 价格：0.02$ / 次

        ### 参数:

        - keyword: 关键词

        - followerRange (可选): 粉丝范围，格式：最小值-最大值
            - 例如：10-100 表示粉丝范围在 10万-100万 之间
            - 不传递此参数则不限制粉丝范围
        - contentTag (可选): 内容标签，支持以下格式:
            - tag-{id}: 一级标签，例如 tag-1 (美妆)
            - tag_level_two-{id}: 二级标签，例如 tag_level_two-7 (穿搭)
            - 标签列表参考文档中的 contentTag 映射表
            - 不传递此参数则不限制内容标签
        ### 返回:

        - kol列表（支持高级筛选）


        # [English]

        ### Purpose:

        - Advanced Search Kol V2, supports follower range and content tag
        filtering

        - The interface data is requested using an enterprise account, which is
        more expensive.

        - Price: 0.02$ / time

        ### Parameters:

        - keyword: Keyword

        - followerRange (optional): Follower range, format: min-max
            - Example: 10-100 indicates follower range between 100,000 and 1,000,000
            - Do not pass this parameter to not limit the follower range
        - contentTag (optional): Content tag, supports the following formats:
            - tag-{id}: First-level tag, e.g., tag-1 (Beauty)
            - tag_level_two-{id}: Second-level tag, e.g., tag_level_two-7 (Outfit)
            - Refer to the contentTag mapping table in the documentation
            - Do not pass this parameter to not limit content tags
        ### Return:

        - Kol List (with advanced filtering)


        # [示例/Example]

        keyword = "美妆"

        followerRange = "10-100"  # 10万-100万粉丝

        contentTag = "tag-1"  # 美妆一级标签

        contentTag = "tag_level_two-2"  # 美妆教程二级标签


        # [内容标签映射表/Content Tag Mapping]


        ## 一级标签 (First-level tags) - 格式: tag-{id}


        | 参数 | 分类 | 参数 | 分类 | 参数 | 分类 |

        |------|------|------|------|------|------|

        | tag-1 | 美妆 | tag-6 | 时尚 | tag-11 | 萌宠 |

        | tag-15 | 测评 | tag-23 | 游戏 | tag-25 | 二次元 |

        | tag-27 | 旅行 | tag-31 | 汽车 | tag-36 | 生活 |

        | tag-41 | 音乐 | tag-46 | 舞蹈* | tag-48 | 美食 |

        | tag-55 | 母婴亲子 | tag-60 | 运动健身 | tag-64 | 科技数码 |

        | tag-68 | 教育培训 | tag-72 | 颜值达人 | tag-79 | 才艺技能 |

        | tag-85 | 影视娱乐 | tag-87 | 艺术文化 | tag-91 | 财经投资 |

        | tag-95 | 三农* | tag-97 | 剧情搞笑 | tag-100 | 情感* |

        | tag-102 | 园艺* | tag-130 | 随拍* | tag-139 | 房产 |

        | tag-1001 | 生活家居 | tag-1002 | 媒体号* | | |


        *注: 标记*的分类无二级标签


        ## 二级标签 (Second-level tags) - 格式: tag_level_two-{id}


        ### 美妆 (tag-1)

        - tag_level_two-2: 美妆教程

        - tag_level_two-3: 妆容展示

        - tag_level_two-4: 护肤保养

        - tag_level_two-5: 美妆测评种草


        ### 时尚 (tag-6)

        - tag_level_two-7: 穿搭

        - tag_level_two-8: 街拍

        - tag_level_two-10: 造型

        - tag_level_two-135: 时尚媒体


        ### 萌宠 (tag-11)

        - tag_level_two-12: 日常宠物

        - tag_level_two-13: 特别宠物

        - tag_level_two-14: 宠物周边


        ### 测评 (tag-15)

        - tag_level_two-16: 美妆测评

        - tag_level_two-17: 3C数码测评

        - tag_level_two-18: 汽车测评

        - tag_level_two-19: 美食产品测评

        - tag_level_two-20: 母婴产品测评

        - tag_level_two-21: 综合测评

        - tag_level_two-132: 酒店测评


        ### 游戏 (tag-23)

        - tag_level_two-121: 游戏剧情

        - tag_level_two-122: 游戏解说

        - tag_level_two-123: 游戏资讯

        - tag_level_two-124: 游戏其他

        - tag_level_two-440: 游戏录屏

        - tag_level_two-441: 游戏集锦


        ### 二次元 (tag-25)

        - tag_level_two-125: 二次元真人

        - tag_level_two-126: 动画漫画

        - tag_level_two-127: 配音声优

        - tag_level_two-128: 宅物手办


        ### 旅行 (tag-27)

        - tag_level_two-28: 旅行记录

        - tag_level_two-29: 旅行攻略

        - tag_level_two-30: 旅行推荐

        - tag_level_two-442: 户外生活


        ### 汽车 (tag-31)

        - tag_level_two-32: 汽车测评

        - tag_level_two-33: 汽车知识

        - tag_level_two-34: 汽车周边


        ### 生活 (tag-36)

        - tag_level_two-37: 生活记录

        - tag_level_two-39: 生活小窍门

        - tag_level_two-40: 好物推荐

        - tag_level_two-118: 健康养生

        - tag_level_two-422: 婚恋


        ### 音乐 (tag-41)

        - tag_level_two-42: 歌曲演唱

        - tag_level_two-43: 乐器演奏

        - tag_level_two-44: 音乐教学

        - tag_level_two-45: 音乐其他

        - tag_level_two-136: 音乐剪辑


        ### 美食 (tag-48)

        - tag_level_two-49: 美食教程

        - tag_level_two-50: 美食探店

        - tag_level_two-52: 美食产品测评

        - tag_level_two-53: 乡村野食

        - tag_level_two-54: 美食其他

        - tag_level_two-423: 酒类


        ### 母婴亲子 (tag-55)

        - tag_level_two-56: 育儿科普

        - tag_level_two-57: 萌娃日常

        - tag_level_two-58: 亲子互动

        - tag_level_two-59: 测评种草


        ### 运动健身 (tag-60)

        - tag_level_two-61: 健身

        - tag_level_two-63: 极限运动

        - tag_level_two-424: 体育资讯

        - tag_level_two-443: 冰雪

        - tag_level_two-444: 垂钓

        - tag_level_two-445: 格斗

        - tag_level_two-446: 球类项目

        - tag_level_two-447: 综合体育


        ### 科技数码 (tag-64)

        - tag_level_two-65: 3C数码

        - tag_level_two-66: 家居电器

        - tag_level_two-133: 科技


        ### 教育培训 (tag-68)

        - tag_level_two-69: 考学培训

        - tag_level_two-70: 语言教学

        - tag_level_two-71: 个人管理

        - tag_level_two-425: 职业教育


        ### 颜值达人 (tag-72)

        - tag_level_two-73: 美女

        - tag_level_two-74: 帅哥


        ### 才艺技能 (tag-79)

        - tag_level_two-80: 创意才能

        - tag_level_two-81: 手工

        - tag_level_two-82: 摄影

        - tag_level_two-83: 绘画

        - tag_level_two-84: 其他才艺


        ### 影视娱乐 (tag-85)

        - tag_level_two-413: 影视解说

        - tag_level_two-414: 影视混剪

        - tag_level_two-415: 明星资讯

        - tag_level_two-416: 综艺解说

        - tag_level_two-417: 综艺混剪


        ### 艺术文化 (tag-87)

        - tag_level_two-88: 传统文化

        - tag_level_two-89: 人文科普

        - tag_level_two-90: 自然科学


        ### 财经投资 (tag-91)

        - tag_level_two-92: 传统金融

        - tag_level_two-93: 互联网金融

        - tag_level_two-94: 财经知识


        ### 剧情搞笑 (tag-97)

        - tag_level_two-98: 剧情

        - tag_level_two-99: 搞笑


        ### 生活家居 (tag-1001)

        - tag_level_two-100101: 硬装

        - tag_level_two-100102: 软装

        - tag_level_two-100103: 生活技巧

        - tag_level_two-100104: 家居氛围


        ### 房产 (tag-139)

        - tag_level_two-140: 其他房产

        - tag_level_two-437: 房产知识

        - tag_level_two-439: 房产及投资

        - tag_level_two-448: 楼盘评测

        - tag_level_two-449: 楼市资讯

        - tag_level_two-450: 租房
      operationId: search_kol_v2_api_v1_douyin_xingtu_search_kol_v2_get
      tags:
        - Douyin-Xingtu-API
        - Douyin-Xingtu-API
      parameters:
        - name: keyword
          in: query
          description: 关键词/Keyword
          required: true
          example: 美妆
          schema:
            type: string
            description: 关键词/Keyword
            title: Keyword
        - name: followerRange
          in: query
          description: 粉丝范围(可选)/Follower Range (optional), 例如 10-100 表示10万-100万粉丝
          required: false
          example: 10-100
          schema:
            type: string
            description: 粉丝范围(可选)/Follower Range (optional), 例如 10-100 表示10万-100万粉丝
            title: Followerrange
        - name: contentTag
          in: query
          description: 内容标签(可选)/Content Tag (optional), 例如 tag-1 或 tag_level_two-7
          required: false
          example: tag-1
          schema:
            type: string
            description: 内容标签(可选)/Content Tag (optional), 例如 tag-1 或 tag_level_two-7
            title: Contenttag
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ResponseModel'
          headers: {}
          x-apifox-name: OK
        '422':
          description: Validation Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/HTTPValidationError'
          headers: {}
          x-apifox-name: Unprocessable Entity
      security:
        - HTTPBearer: []
          x-apifox:
            schemeGroups:
              - id: 3Mi6srg_lMnZHlqD_Og9P
                schemeIds:
                  - HTTPBearer
            required: true
            use:
              id: 3Mi6srg_lMnZHlqD_Og9P
            scopes:
              3Mi6srg_lMnZHlqD_Og9P:
                HTTPBearer: []
      x-apifox-folder: Douyin-Xingtu-API
      x-apifox-status: released
      x-run-in-apifox: https://app.apifox.com/web/project/4705614/apis/api-383041376-run
components:
  schemas:
    ResponseModel:
      properties:
        code:
          type: integer
          title: Code
          description: HTTP status code | HTTP状态码
          default: 200
        request_id:
          anyOf:
            - type: string
            - type: 'null'
          title: Request Id
          description: Unique request identifier | 唯一请求标识符
        message:
          type: string
          title: Message
          description: Response message (EN-US) | 响应消息 (English)
          default: Request successful. This request will incur a charge.
        message_zh:
          type: string
          title: Message Zh
          description: Response message (ZH-CN) | 响应消息 (中文)
          default: 请求成功，本次请求将被计费。
        support:
          type: string
          title: Support
          description: Support message | 支持消息
          default: 'Discord: https://discord.gg/aMEAS8Xsvz'
        time:
          type: string
          title: Time
          description: The time the response was generated | 生成响应的时间
        time_stamp:
          type: integer
          title: Time Stamp
          description: The timestamp the response was generated | 生成响应的时间戳
        time_zone:
          type: string
          title: Time Zone
          description: The timezone of the response time | 响应时间的时区
          default: America/Los_Angeles
        docs:
          anyOf:
            - type: string
            - type: 'null'
          title: Docs
          description: >-
            Link to the API Swagger documentation for this endpoint | 此端点的 API
            Swagger 文档链接
        cache_message:
          anyOf:
            - type: string
            - type: 'null'
          title: Cache Message
          description: Cache message (EN-US) | 缓存消息 (English)
          default: >-
            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:
          anyOf:
            - type: string
            - type: 'null'
          title: Cache Message Zh
          description: Cache message (ZH-CN) | 缓存消息 (中文)
          default: >-
            本次响应已缓存，可通过下方 URL 直接查看，有效期 24
            小时，访问缓存链接无额外费用。缓存仅用于请求溯源，不影响接口数据的时效性，也不会再次通过接口返回。
        cache_url:
          anyOf:
            - type: string
            - type: 'null'
          title: Cache Url
          description: The URL to access the cached result | 访问缓存结果的 URL
        router:
          type: string
          title: Router
          description: The endpoint that generated this response | 生成此响应的端点
          default: ''
        params:
          type: string
        data:
          anyOf:
            - type: string
            - type: 'null'
          title: Data
          description: The response data | 响应数据
      type: object
      title: ResponseModel
      x-apifox-orders:
        - code
        - request_id
        - message
        - message_zh
        - support
        - time
        - time_stamp
        - time_zone
        - docs
        - cache_message
        - cache_message_zh
        - cache_url
        - router
        - params
        - data
      x-apifox-ignore-properties: []
      x-apifox-folder: ''
    HTTPValidationError:
      properties:
        detail:
          items:
            $ref: '#/components/schemas/ValidationError'
          type: array
          title: Detail
      type: object
      title: HTTPValidationError
      x-apifox-orders:
        - detail
      x-apifox-ignore-properties: []
      x-apifox-folder: ''
    ValidationError:
      properties:
        loc:
          items:
            anyOf:
              - type: string
              - type: integer
          type: array
          title: Location
        msg:
          type: string
          title: Message
        type:
          type: string
          title: Error Type
      type: object
      required:
        - loc
        - msg
        - type
      title: ValidationError
      x-apifox-orders:
        - loc
        - msg
        - type
      x-apifox-ignore-properties: []
      x-apifox-folder: ''
  securitySchemes:
    HTTPBearer:
      type: bearer
      description: >
        ----

        #### API Token Introduction:

        ##### Method 1: Use API Token in the Request Header (Recommended)

        - **Header**: `Authorization`

        - **Format**: `Bearer {token}`

        - **Example**: `{"Authorization": "Bearer your_token"}`

        - **Swagger UI**: Click on the `Authorize` button in the upper right
        corner of the page to enter the API token directly without the `Bearer`
        keyword.


        ##### Method 2: Use API Token in the Cookie (Not Recommended, Use Only
        When Method 1 is Unavailable)

        - **Cookie**: `Authorization`

        - **Format**: `Bearer {token}`

        - **Example**: `Authorization=Bearer your_token`


        #### Get API Token:

        1. Register and log in to your account on the TikHub website.

        2. Go to the user center, click on the API token menu, and create an API
        token.

        3. Copy and use the API token in the request header.

        4. Keep your API token confidential and use it only in the request
        header.


        ----


        #### API令牌简介:

        ##### 方法一：在请求头中使用API令牌（推荐）

        - **请求头**: `Authorization`

        - **格式**: `Bearer {token}`

        - **示例**: `{"Authorization": "Bearer your_token"}`

        - **Swagger UI**: 点击页面右上角的`Authorize`按钮，直接输入API令牌，不需要`Bearer`关键字。


        ##### 方法二：在Cookie中使用API令牌（不推荐，仅在无法使用方法一时使用）

        - **Cookie**: `Authorization`

        - **格式**: `Bearer {token}`

        - **示例**: `Authorization=Bearer your_token`


        #### 获取API令牌:

        1. 在TikHub网站注册并登录账户。

        2. 进入用户中心，点击API令牌菜单，创建API令牌。

        3. 复制并在请求头中使用API令牌。

        4. 保密您的API令牌，仅在请求头中使用。
      scheme: bearer
servers:
  - url: https://api.tikhub.io
    description: Production Environment
security: []

```
