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

## OpenAPI Specification

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

        ### 用途:

        - 获取帖子评论的回复（二级评论）


        ### 参数详解:


        #### 必选参数:

        **continuation_token** (string)

        - **作用**: 回复的continuation token

        - **获取方式**: 从帖子一级评论的响应数据中获取 `reply_continuation_token` 字段


        #### 可选参数:

        **language_code** (string, 可选) - 语言代码，默认 `"zh-CN"`


        **country_code** (string, 可选) - 国家代码，默认 `"US"`


        **need_format** (bool, 可选) - 是否格式化数据，默认 `true`


        ### 使用流程:

        1. 先调用 `/get_post_comments` 获取帖子一级评论

        2. 从一级评论中找到 `reply_continuation_token` 字段

        3. 使用该 token 调用本接口获取该评论的所有回复

        4. 如果还有更多回复，使用返回的 `continuation_token` 继续获取


        ### 返回数据 (need_format=true):

        - comments: 回复评论列表
          - comment_id: 评论ID
          - content: 评论内容文本
          - published_time: 发布时间
          - like_count: 点赞数
          - author: 作者信息
        - continuation_token: 下一页token（如果有更多回复）


        ### 价格:

        - $0.001 USD / 请求


        # [English]

        ### Purpose:

        - Get replies to a post comment (second-level comments)


        ### Parameters:


        #### Required:

        **continuation_token** (string)

        - **Purpose**: Reply continuation token

        - **How to get**: Extract `reply_continuation_token` from post comment
        response


        #### Optional:

        **language_code** (string, optional) - Language code, default `"zh-CN"`


        **country_code** (string, optional) - Country code, default `"US"`


        **need_format** (bool, optional) - Whether to format data, default
        `true`


        ### Usage Flow:

        1. Get post comments via `/get_post_comments`

        2. Extract `reply_continuation_token` from a comment with replies

        3. Pass it as `continuation_token` to this endpoint

        4. Use returned `continuation_token` for more replies


        ### Returns (need_format=true):

        - comments: Reply comments list

        - continuation_token: Next page token (if more replies)


        ### Price:

        - $0.001 USD / request


        ### [示例/Example]

        #### GET
        /get_post_comment_replies?continuation_token=xxx&need_format=true
      operationId: >-
        get_post_comment_replies_api_v1_youtube_web_v2_get_post_comment_replies_get
      tags:
        - YouTube-Web-V2-API
        - YouTube-Web-V2-API
      parameters:
        - name: continuation_token
          in: query
          description: >-
            回复的continuation token（从帖子评论的 reply_continuation_token 字段获取）/Reply
            continuation token from post comment
          required: true
          schema:
            type: string
            description: >-
              回复的continuation token（从帖子评论的 reply_continuation_token 字段获取）/Reply
              continuation token from post comment
            title: Continuation Token
        - name: language_code
          in: query
          description: 语言代码（如zh-CN, en-US等）/Language code
          required: false
          example: zh-CN
          schema:
            type: string
            description: 语言代码（如zh-CN, en-US等）/Language code
            default: zh-CN
            title: Language Code
        - name: country_code
          in: query
          description: 国家代码（如US, JP等）/Country code
          required: false
          example: US
          schema:
            type: string
            description: 国家代码（如US, JP等）/Country code
            default: US
            title: Country Code
        - name: need_format
          in: query
          description: 是否需要清洗数据，提取关键内容，移除冗余数据/Whether to clean and format the data
          required: false
          schema:
            type: boolean
            description: 是否需要清洗数据，提取关键内容，移除冗余数据/Whether to clean and format the data
            default: true
            title: Need Format
      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: vNoaFAYtCgihPlV23JA0-
                schemeIds:
                  - HTTPBearer
            required: true
            use:
              id: vNoaFAYtCgihPlV23JA0-
            scopes:
              vNoaFAYtCgihPlV23JA0-:
                HTTPBearer: []
      x-apifox-folder: YouTube-Web-V2-API
      x-apifox-status: released
      x-run-in-apifox: https://app.apifox.com/web/project/4705614/apis/api-440187735-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: []

```