# 获取评论的子评论/回复/Get comment replies

## OpenAPI Specification

```yaml
openapi: 3.0.1
info:
  title: ''
  description: ''
  version: 1.0.0
paths:
  /api/v1/instagram/v3/get_comment_replies:
    get:
      summary: 获取评论的子评论/回复/Get comment replies
      deprecated: false
      description: >-
        # [中文]

        ### 用途:

        - 获取Instagram评论的子评论（回复）列表

        - 支持分页获取所有回复

        - 父评论的 comment_id 可从 get_post_comments 接口的评论列表中获取

        ### 参数:

        - media_id: 帖子的媒体ID（数字ID，必填），可通过 `/shortcode_to_media_id` 接口从短码转换获得

        - comment_id: 父评论ID（必填，从 get_post_comments 返回的评论中获取 `pk` 字段）

        - min_id: 分页游标，首次请求不传，从上一次响应的 `data.next_min_child_cursor` 获取

        ### 返回:

        - `data.child_comments`: 子评论列表
            - `user`: 评论者信息
            - `text`: 评论文本
            - `created_at`: 评论时间戳
            - `comment_like_count`: 评论点赞数
            - `pk`: 评论ID
        - `data.next_min_child_cursor`: 下一页分页游标（传给下次请求的min_id参数）

        - `data.has_more_tail_child_comments`: 是否有更多子评论

        - `data.num_tail_child_comments`: 剩余子评论数

        ### 分页使用方法:

        1. 首次请求：传 `media_id` 和 `comment_id` 参数

        2. 获取响应中的 `data.next_min_child_cursor`

        3. 下次请求：将 `next_min_child_cursor` 原样传入 `min_id` 参数（无需预处理，接口会自动反转义）

        4. 重复步骤 2-3 直到 `data.has_more_tail_child_comments` 为 false


        ### 注意:

        - `min_id` 可能是转义 JSON 字符串（如 `{"key":"val"}`），直接原样传入即可，接口内部会自动反转义处理

        ### 价格:

        - 0.008 USD/请求


        # [English]

        ### Purpose:

        - Get Instagram comment's child comments (replies) list

        - Support pagination to fetch all replies

        - Parent comment's comment_id can be obtained from get_post_comments API

        ### Parameters:

        - media_id: Post media ID (numeric ID, required), can be obtained via
        `/shortcode_to_media_id` endpoint

        - comment_id: Parent comment ID (required, get `pk` field from
        get_post_comments response)

        - min_id: Pagination cursor, omit for first request, get from previous
        response `data.next_min_child_cursor`

        ### Return:

        - `data.child_comments`: Child comments list
            - `user`: Commenter info
            - `text`: Comment text
            - `created_at`: Comment timestamp
            - `comment_like_count`: Comment likes count
            - `pk`: Comment ID
        - `data.next_min_child_cursor`: Next page cursor (use as min_id in next
        request)

        - `data.has_more_tail_child_comments`: Whether has more child comments

        - `data.num_tail_child_comments`: Remaining child comments count

        ### Pagination usage:

        1. First request: Pass `media_id` and `comment_id` parameters

        2. Get `data.next_min_child_cursor` from response

        3. Next request: Pass `next_min_child_cursor` as-is to `min_id`
        parameter (no pre-processing needed, the API handles unescaping
        automatically)

        4. Repeat steps 2-3 until `data.has_more_tail_child_comments` is false


        ### Note:

        - `min_id` may be an escaped JSON string (e.g. `{"key":"val"}`), just
        pass it as-is, the API handles unescaping internally

        ### Price:

        - 0.008 USD/request


        ### 示例/Example

        media_id = "3829530490739515971"

        comment_id = "18065937092249736"
      operationId: get_comment_replies_api_v1_instagram_v3_get_comment_replies_get
      tags:
        - Instagram-V3-API
        - Instagram-V3-API
      parameters:
        - name: media_id
          in: query
          description: 帖子媒体ID/Post media ID
          required: true
          example: '3829530490739515971'
          schema:
            type: string
            description: 帖子媒体ID/Post media ID
            title: Media Id
        - name: comment_id
          in: query
          description: 父评论ID/Parent comment ID
          required: true
          example: '18065937092249736'
          schema:
            type: string
            description: 父评论ID/Parent comment ID
            title: Comment Id
        - name: min_id
          in: query
          description: >-
            分页游标，首次请求不传，从上一次响应的 next_min_child_cursor 获取/Pagination cursor, omit
            for first request, get from previous response next_min_child_cursor
          required: false
          schema:
            type: string
            description: >-
              分页游标，首次请求不传，从上一次响应的 next_min_child_cursor 获取/Pagination cursor,
              omit for first request, get from previous response
              next_min_child_cursor
            title: Min Id
      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: ZlygeV6hxA5LQ_GyAYF_7
                schemeIds:
                  - HTTPBearer
            required: true
            use:
              id: ZlygeV6hxA5LQ_GyAYF_7
            scopes:
              ZlygeV6hxA5LQ_GyAYF_7:
                HTTPBearer: []
      x-apifox-folder: Instagram-V3-API
      x-apifox-status: released
      x-run-in-apifox: https://app.apifox.com/web/project/4705614/apis/api-419083072-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: []

```