# 互动趋势/Content interact trend

## OpenAPI Specification

```yaml
openapi: 3.0.1
info:
  title: ''
  description: ''
  version: 1.0.0
paths:
  /api/v1/douyin/index/fetch_content_interact_trend:
    post:
      summary: 互动趋势/Content interact trend
      deprecated: false
      description: >-
        # [中文]

        ### 用途:

        - 获取指定垂类的互动数据（点赞/评论/分享/收藏等）随时间变化趋势

        - 衡量该垂类内容引发用户互动的活跃程度

        ### 参数:

        - tag_id: 垂类ID（**必填，不支持 0=全部**，需传入具体垂类 ID，可通过 fetch_item_filter_options
        获取）

        - start_date: 起始日期 YYYYMMDD（含）

        - end_date: 结束日期 YYYYMMDD（含）

        ### 返回:

        - 按日聚合的互动数据：每日点赞总数、评论总数、分享总数、收藏总数等


        # [English]

        ### Purpose:

        - Get interaction (like/comment/share/favorite) trend over time for a
        category

        - Measures user engagement intensity for content in this category

        ### Parameters:

        - tag_id: Category ID (**required, does NOT support 0=all**, must pass a
        specific category ID)

        - start_date: Start date YYYYMMDD (inclusive)

        - end_date: End date YYYYMMDD (inclusive)

        ### Return:

        - Daily aggregated interaction data: like / comment / share / favorite
        totals per day


        # [示例/Example]

        tag_id = "601"

        start_date = "20260314"

        end_date = "20260414"
      operationId: >-
        fetch_content_interact_trend_api_v1_douyin_index_fetch_content_interact_trend_post
      tags:
        - Douyin-Index-API
        - Douyin-Index-API
      parameters:
        - name: tag_id
          in: query
          description: >-
            垂类ID，**必填，不支持 0=全部**（同 fetch_item_query 的 category_id 但不接受
            0）/Category ID, **required, does NOT support 0=all**. Get full list
            via fetch_item_filter_options (excluding id=0)
          required: true
          schema:
            type: string
            description: >-
              垂类ID，**必填，不支持 0=全部**（同 fetch_item_query 的 category_id 但不接受
              0）/Category ID, **required, does NOT support 0=all**. Get full
              list via fetch_item_filter_options (excluding id=0)
            title: Tag Id
        - name: start_date
          in: query
          description: 开始日期/Start date YYYYMMDD
          required: true
          schema:
            type: string
            description: 开始日期/Start date YYYYMMDD
            title: Start Date
        - name: end_date
          in: query
          description: 结束日期/End date YYYYMMDD
          required: true
          schema:
            type: string
            description: 结束日期/End date YYYYMMDD
            title: End Date
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ResponseModel'
          headers: {}
          x-apifox-name: ''
        '422':
          description: Validation Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/HTTPValidationError'
          headers: {}
          x-apifox-name: ''
      security:
        - HTTPBearer: []
          x-apifox:
            schemeGroups:
              - id: L6buG0FKLFsZtBPAiLVwJ
                schemeIds:
                  - HTTPBearer
            required: true
            use:
              id: L6buG0FKLFsZtBPAiLVwJ
            scopes:
              L6buG0FKLFsZtBPAiLVwJ:
                HTTPBearer: []
      x-apifox-folder: Douyin-Index-API
      x-apifox-status: released
      x-run-in-apifox: https://app.apifox.com/web/project/4705614/apis/api-444247770-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: []

```