# 搜索趋势报告/Search trend reports

## OpenAPI Specification

```yaml
openapi: 3.0.1
info:
  title: ''
  description: ''
  version: 1.0.0
paths:
  /api/v1/douyin/index/fetch_report_search:
    post:
      summary: 搜索趋势报告/Search trend reports
      deprecated: false
      description: |-
        # [中文]
        ### 用途:
        - 搜索抖音指数下的趋势报告，支持类型/产品/年份/关键词四维筛选
        ### 参数:
        - current_page / page_size: 分页参数（字符串）
        - type: 报告类型，空字符串表示全部
            - "行业洞察" / "产品洞察" / "用户洞察" / "趋势洞察"
        - business: 所属产品（逗号分隔），可选值：
            - "巨量引擎", "今日头条", "抖音", "西瓜视频", "抖音电商", "仕小禄", "其他"
        - report_time: 发布年份（逗号分隔），如 "2024,2023"
        - search: 报告标题关键词
        - category: 顶层分类ID，默认 "6"（抖音指数趋势报告固定值，一般无需修改）
        ### 返回:
        - 报告列表（标题、封面、发布时间、产品标签、报告ID 等）

        # [English]
        ### Purpose:
        - Search trend insight reports under Douyin Index
        ### Parameters:
        - current_page / page_size: pagination (string)
        - type: report type, empty for all
        - business: comma-separated product list
        - report_time: comma-separated year list, e.g. "2024,2023"
        - search: keyword search
        - category: top-level category ID, default "6"

        # [示例/Example]
        type = "行业洞察"
        business = "巨量引擎"
        report_time = "2024"
        search = "公路"
      operationId: fetch_report_search_api_v1_douyin_index_fetch_report_search_post
      tags:
        - Douyin-Index-API
        - Douyin-Index-API
      parameters:
        - name: current_page
          in: query
          description: 页码/Page number
          required: false
          schema:
            type: string
            description: 页码/Page number
            default: '1'
            title: Current Page
        - name: page_size
          in: query
          description: 每页数量/Page size
          required: false
          schema:
            type: string
            description: 每页数量/Page size
            default: '16'
            title: Page Size
        - name: type
          in: query
          description: >-
            报告类型/Report type: 空=全部, 行业洞察=Industry, 产品洞察=Product, 用户洞察=User,
            趋势洞察=Trend
          required: false
          schema:
            enum:
              - ''
              - 行业洞察
              - 产品洞察
              - 用户洞察
              - 趋势洞察
            type: string
            description: >-
              报告类型/Report type: 空=全部, 行业洞察=Industry, 产品洞察=Product, 用户洞察=User,
              趋势洞察=Trend
            default: ''
            title: Type
        - name: business
          in: query
          description: >-
            所属产品列表，逗号分隔/Business list, comma separated. Options: 巨量引擎, 今日头条, 抖音,
            西瓜视频, 抖音电商, 仕小禄, 其他
          required: false
          schema:
            type: string
            description: >-
              所属产品列表，逗号分隔/Business list, comma separated. Options: 巨量引擎, 今日头条,
              抖音, 西瓜视频, 抖音电商, 仕小禄, 其他
            default: ''
            title: Business
        - name: report_time
          in: query
          description: 发布年份列表，逗号分隔/Year list, comma separated. e.g. 2024,2023
          required: false
          schema:
            type: string
            description: 发布年份列表，逗号分隔/Year list, comma separated. e.g. 2024,2023
            default: ''
            title: Report Time
        - name: search
          in: query
          description: 报告关键词搜索/Search keyword
          required: false
          schema:
            type: string
            description: 报告关键词搜索/Search keyword
            default: ''
            title: Search
        - name: category
          in: query
          description: >-
            顶层分类ID（默认 6 表示抖音指数趋势报告）/Top category ID (default 6 = Douyin Index
            trend reports)
          required: false
          schema:
            type: string
            description: >-
              顶层分类ID（默认 6 表示抖音指数趋势报告）/Top category ID (default 6 = Douyin Index
              trend reports)
            default: '6'
            title: Category
      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: wSS6GpXACpSEq8b56xgsX
                schemeIds:
                  - HTTPBearer
            required: true
            use:
              id: wSS6GpXACpSEq8b56xgsX
            scopes:
              wSS6GpXACpSEq8b56xgsX:
                HTTPBearer: []
      x-apifox-folder: Douyin-Index-API
      x-apifox-status: released
      x-run-in-apifox: https://app.apifox.com/web/project/4705614/apis/api-444247773-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: []

```
