# 获取作品观众其他数据分析/Fetch item audience others analysis

## OpenAPI Specification

```yaml
openapi: 3.0.1
info:
  title: ''
  description: ''
  version: 1.0.0
paths:
  /api/v1/douyin/creator_v2/fetch_item_audience_others:
    post:
      summary: 获取作品观众其他数据分析/Fetch item audience others analysis
      deprecated: false
      description: >-
        # [中文]

        ### 用途:

        - 获取抖音作品的观众其他数据分析，包括受众分布和受众关注词

        - 了解观众是否为粉丝，以及观众关注的兴趣话题

        - **此接口需要用户提供有效的抖音创作者平台Cookie**

        - **使用 POST 方法，Cookie 在请求体中传输，更安全**


        ### 请求体参数:

        - cookie: 用户的抖音创作者平台Cookie（必填，在请求体中传输）

        - item_id: 作品ID（必填）


        ### 返回数据说明:

        - **audience_distribution (受众分布)**:
          - fan_list: 粉丝占比列表
            - key: "1"=粉丝, "0"=非粉丝
            - value: 占比（0-1之间的小数）

        - **audience_keyword (受众关注词)**:
          - keyword_list: 观众关注的话题/关键词列表
            - keyword: 关键词内容
            - value: 该关键词的关注度占比

        ### Cookie 获取方式:

        1. 登录抖音创作者平台 (https://creator.douyin.com)

        2. 打开浏览器开发者工具（F12）

        3. 切换到 Network 标签

        4. 刷新页面或进行操作

        5. 找到任意请求，复制 Cookie 请求头的值


        # [English]

        ### Purpose:

        - Get Douyin item audience other data analysis, including audience
        distribution and audience keywords

        - Understand whether the audience are fans and what topics they are
        interested in

        - **This API requires users to provide valid Douyin Creator Platform
        Cookie**

        - **Use POST method, Cookie is transmitted in request body, more
        secure**


        ### Request Body Parameters:

        - cookie: User's Douyin Creator Platform Cookie (required, transmitted
        in request body)

        - item_id: Item ID (required)


        ### Return Data Description:

        - **audience_distribution (Audience Distribution)**:
          - fan_list: Fan proportion list
            - key: "1"=Fan, "0"=Non-fan
            - value: Proportion (decimal between 0-1)

        - **audience_keyword (Audience Keywords)**:
          - keyword_list: List of topics/keywords that audiences are interested in
            - keyword: Keyword content
            - value: Interest proportion for this keyword

        ### How to get Cookie:

        1. Login to Douyin Creator Platform (https://creator.douyin.com)

        2. Open browser developer tools (F12)

        3. Switch to Network tab

        4. Refresh page or perform operations

        5. Find any request and copy the Cookie header value


        # [示例/Example]

        ```json

        {
            "cookie": "Your_Cookie_Here",
            "item_id": "7559536212910853422"
        }

        ```


        ### 返回数据示例/Response Example:

        ```json

        {
            "audience_distribution": {
                "fan_list": [
                    {
                        "key": "1",
                        "value": 0.156
                    },
                    {
                        "key": "0",
                        "value": 0.844
                    }
                ]
            },
            "audience_keyword": {
                "keyword_list": [
                    {
                        "keyword": "美食",
                        "value": 0.35
                    },
                    {
                        "keyword": "旅游",
                        "value": 0.28
                    },
                    {
                        "keyword": "生活",
                        "value": 0.22
                    },
                    {
                        "keyword": "娱乐",
                        "value": 0.15
                    }
                ]
            },
            "status_code": 0,
            "status_msg": ""
        }

        ```


        ### 数据解读/Data Interpretation:


        **受众分布 (audience_distribution)**:

        - key="1": 表示粉丝，value=0.156 表示15.6%的观众是已关注的粉丝

        - key="0": 表示非粉丝，value=0.844 表示84.4%的观众是未关注的路人

        - 粉丝占比高说明内容对现有粉丝吸引力强

        - 非粉丝占比高说明作品破圈能力强，吸引了很多新观众


        **受众关注词 (audience_keyword)**:

        - keyword_list展示观众群体关注的其他话题

        - 可以了解观众的兴趣偏好，用于内容规划

        - 示例中观众主要关注"美食"(35%)、"旅游"(28%)等话题

        - 可以结合这些关键词创作相关内容，提高吸引力


        ### 优化建议/Optimization Suggestions:

        1. **粉丝维护**: 如果粉丝占比高(>30%)，说明内容符合粉丝预期，继续保持风格

        2. **破圈拓展**: 如果非粉丝占比高(>80%)，说明内容有爆款潜力，可加大推广

        3. **内容规划**: 根据audience_keyword规划相关主题内容，覆盖观众兴趣点

        4. **跨界合作**: 结合高占比关键词，进行跨领域内容创作

        5. **粉丝转化**: 对于非粉丝占比高的爆款作品，在评论区引导关注

        6. **兴趣匹配**: 关注观众兴趣词与作品内容的匹配度，调整内容方向

        7. **话题借势**: 利用观众关注的热门话题，制作相关内容蹭热度

        8. **受众画像**: 结合关注词描绘完整的受众兴趣画像


        ### 注意事项/Notes:

        - 观众数据需要一定播放量才准确，建议作品有1000+播放后查看

        - 数据可能有延迟，通常在作品发布24-48小时后更新

        - 粉丝占比与作品是否爆款无关，重点看内容质量和推广效果

        - 受众关注词反映的是观众整体兴趣，不一定与当前作品主题相关

        - 如果返回空列表，说明该作品目前暂无足够数据

        - 结合其他数据（如观众画像）综合分析效果更好
      operationId: >-
        fetch_item_audience_others_api_v1_douyin_creator_v2_fetch_item_audience_others_post
      tags:
        - Douyin-Creator-V2-API
        - Douyin-Creator-V2-API
      parameters: []
      requestBody:
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/ItemAudienceOthersRequest'
              description: 作品观众其他数据分析请求参数/Item audience others analysis request parameters
            example:
              cookie: Your_Cookie_Here
              item_id: '7559536212910853422'
      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: GXYAZ-bR5QRuhEzr5MrWT
                schemeIds:
                  - HTTPBearer
            required: true
            use:
              id: GXYAZ-bR5QRuhEzr5MrWT
            scopes:
              GXYAZ-bR5QRuhEzr5MrWT:
                HTTPBearer: []
      x-apifox-folder: Douyin-Creator-V2-API
      x-apifox-status: released
      x-run-in-apifox: https://app.apifox.com/web/project/4705614/apis/api-359719867-run
components:
  schemas:
    ItemAudienceOthersRequest:
      properties:
        cookie:
          type: string
          title: Cookie
          description: 用户Cookie/User Cookie
          examples:
            - Your_Cookie_Here
        item_id:
          type: string
          title: Item Id
          description: 作品ID/Item ID
          examples:
            - '7559536212910853422'
      type: object
      required:
        - cookie
        - item_id
      title: ItemAudienceOthersRequest
      description: |-
        作品观众其他数据分析请求模型
        Item Audience Others Request Model
      x-apifox-orders:
        - cookie
        - item_id
      x-apifox-ignore-properties: []
      x-apifox-folder: ''
    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: []

```