# 获取话题笔记列表/Get topic feed

## OpenAPI Specification

```yaml
openapi: 3.0.1
info:
  title: ''
  description: ''
  version: 1.0.0
paths:
  /api/v1/xiaohongshu/app_v2/get_topic_feed:
    get:
      summary: 获取话题笔记列表/Get topic feed
      deprecated: false
      description: >-
        # [中文]

        ### 用途:

        - 获取指定话题下的笔记列表，支持按最热或最新排序，使用游标分页

        ### ⚠️ 计费提示:

        - 如果传入错误或不存在的话题页面ID，接口仍会正常响应，但 `data` 中会返回上游"服务异常"信息，该请求
        **同样会正常计费扣费**，请在调用前确保参数有效。

        ### 参数:

        - page_id: 话题页面ID（必需），如 "5c1cc866febed9000184b7c1"
            - 可以从单一笔记接口获取或搜索接口
        - sort: 排序方式
            - "trend": 最热（默认）
            - "time": 最新
        - cursor_score: 分页游标分数，翻页时传入上一页最后一个 item 的 cursor_score

        - last_note_id: 上一页最后一条笔记ID，翻页时传入

        - last_note_ct: 上一页最后一条笔记创建时间，翻页时传入

        - session_id: 会话ID，翻页时保持一致

        - first_load_time: 首次加载时间戳，翻页时保持一致

        - source: 来源，默认 "normal"

        ### 返回:

        - 话题笔记列表数据

        ### 翻页说明:

        - 首次请求：只传 page_id 和 sort，其余留空

        - 翻页请求：取上一次响应最后一个 item 的字段:
            - cursor_score ← items[-1].cursor_score
            - last_note_id ← items[-1].id
            - last_note_ct ← items[-1].create_time
        - 建议同时回传 session_id 和 first_load_time 保持会话一致


        # [English]

        ### Purpose:

        - Get notes list under a specified topic, supports sorting by trending
        or latest, using cursor pagination

        ### ⚠️ Billing Notice:

        - If a wrong or non-existent topic page ID is passed, the endpoint still
        responds normally, but the `data` field will contain an upstream
        "service error" message. Such requests **will still be billed as
        normal**. Please make sure the parameters are valid before calling.

        ### Parameters:

        - page_id: Topic page ID (required), e.g. "5c1cc866febed9000184b7c1"
            - Can be obtained from single note API or search API
        - sort: Sort type
            - "trend": Trending (default)
            - "time": Latest
        - cursor_score: Pagination cursor score, pass last item's cursor_score
        from previous response

        - last_note_id: Last note ID from previous page

        - last_note_ct: Last note create time from previous page

        - session_id: Session ID, keep consistent for pagination

        - first_load_time: First load timestamp, keep consistent for pagination

        - source: Source, default "normal"

        ### Return:

        - Topic notes list data

        ### Pagination Guide:

        - First request: only pass page_id and sort, leave others empty

        - Next page: pass fields from last item of previous response:
            - cursor_score ← items[-1].cursor_score
            - last_note_id ← items[-1].id
            - last_note_ct ← items[-1].create_time
        - Recommended to also pass session_id and first_load_time for session
        consistency


        # [示例/Example]

        page_id="5c1cc866febed9000184b7c1"

        sort="trend"
      operationId: get_topic_feed_api_v1_xiaohongshu_app_v2_get_topic_feed_get
      tags:
        - Xiaohongshu-App-V2-API
        - Xiaohongshu-App-V2-API
      parameters:
        - name: page_id
          in: query
          description: 话题页面ID/Topic page ID
          required: true
          example: 5c1cc866febed9000184b7c1
          schema:
            type: string
            description: 话题页面ID/Topic page ID
            title: Page Id
        - name: sort
          in: query
          description: '排序方式/Sort: trend(最热), time(最新)'
          required: false
          example: trend
          schema:
            type: string
            description: '排序方式/Sort: trend(最热), time(最新)'
            default: trend
            title: Sort
        - name: cursor_score
          in: query
          description: 分页游标分数，翻页时传入/Pagination cursor score for next page
          required: false
          example: ''
          schema:
            type: string
            description: 分页游标分数，翻页时传入/Pagination cursor score for next page
            default: ''
            title: Cursor Score
        - name: last_note_id
          in: query
          description: 上一页最后一条笔记ID，翻页时传入/Last note ID from previous page
          required: false
          example: ''
          schema:
            type: string
            description: 上一页最后一条笔记ID，翻页时传入/Last note ID from previous page
            default: ''
            title: Last Note Id
        - name: last_note_ct
          in: query
          description: 上一页最后一条笔记创建时间，翻页时传入/Last note create time from previous page
          required: false
          example: ''
          schema:
            type: string
            description: 上一页最后一条笔记创建时间，翻页时传入/Last note create time from previous page
            default: ''
            title: Last Note Ct
        - name: session_id
          in: query
          description: 会话ID，翻页时保持一致/Session ID, keep consistent for pagination
          required: false
          example: ''
          schema:
            type: string
            description: 会话ID，翻页时保持一致/Session ID, keep consistent for pagination
            default: ''
            title: Session Id
        - name: first_load_time
          in: query
          description: 首次加载时间戳，翻页时保持一致/First load timestamp, keep consistent for pagination
          required: false
          example: ''
          schema:
            type: string
            description: >-
              首次加载时间戳，翻页时保持一致/First load timestamp, keep consistent for
              pagination
            default: ''
            title: First Load Time
        - name: source
          in: query
          description: 来源/Source
          required: false
          example: normal
          schema:
            type: string
            description: 来源/Source
            default: normal
            title: Source
      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: rkaJ4yWWCC7kZyjrYVl8z
                schemeIds:
                  - HTTPBearer
            required: true
            use:
              id: rkaJ4yWWCC7kZyjrYVl8z
            scopes:
              rkaJ4yWWCC7kZyjrYVl8z:
                HTTPBearer: []
      x-apifox-folder: Xiaohongshu-App-V2-API
      x-apifox-status: released
      x-run-in-apifox: https://app.apifox.com/web/project/4705614/apis/api-420136408-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: []

```