# 获取Reels推荐列表/Get recommended Reels feed

## OpenAPI Specification

```yaml
openapi: 3.0.1
info:
  title: ''
  description: ''
  version: 1.0.0
paths:
  /api/v1/instagram/v3/get_recommended_reels:
    get:
      summary: 获取Reels推荐列表/Get recommended Reels feed
      deprecated: false
      description: >-
        # [中文]

        ### 用途:

        - 获取Instagram Reels推荐列表

        - 支持分页获取更多Reels

        ### 参数:

        - first: 每次获取的Reels数量（默认12，最大50）

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

        ### 返回:

        - `data.edges`: Reels列表
            - `node.media`: Reels媒体信息
                - `code`: 帖子短代码
                - `pk`: 帖子ID
                - `like_count`: 点赞数
                - `comment_count`: 评论数
                - `play_count`: 播放数
                - `caption.text`: 描述文本
                - `user`: 发布者信息
                - `video_versions`: 视频版本列表
                - `image_versions2`: 封面图版本列表
        - `data.page_info`: 分页信息
            - `has_next_page`: 是否有下一页
            - `end_cursor`: 下一页游标（传给下次请求的after参数）
        ### 分页使用方法:

        1. 首次请求：只传 `first` 参数

        2. 获取响应中的 `data.page_info.end_cursor`

        3. 下次请求：传入 `first` 和 `after` (使用上次的end_cursor)

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

        ### 价格:

        - 0.008 USD/请求


        # [English]

        ### Purpose:

        - Get Instagram Reels recommendation feed

        - Support pagination to fetch more Reels

        ### Parameters:

        - first: Number of Reels to fetch per request (default 12, max 50)

        - after: Pagination cursor, omit for first request, get from previous
        response `data.page_info.end_cursor`

        ### Return:

        - `data.edges`: Reels list
            - `node.media`: Reels media info
                - `code`: Post shortcode
                - `pk`: Post ID
                - `like_count`: Likes count
                - `comment_count`: Comments count
                - `play_count`: Play count
                - `caption.text`: Description text
                - `user`: Publisher info
                - `video_versions`: Video version list
                - `image_versions2`: Cover image version list
        - `data.page_info`: Pagination info
            - `has_next_page`: Whether has next page
            - `end_cursor`: Next page cursor (use as after parameter in next request)
        ### Pagination usage:

        1. First request: Only pass `first` parameter

        2. Get `data.page_info.end_cursor` from response

        3. Next request: Pass `first` and `after` (use end_cursor from previous)

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

        ### Price:

        - 0.008 USD/request


        ### 示例/Example

        first = 12
      operationId: get_recommended_reels_api_v1_instagram_v3_get_recommended_reels_get
      tags:
        - Instagram-V3-API
        - Instagram-V3-API
      parameters:
        - name: first
          in: query
          description: 获取数量/Number of reels to fetch
          required: false
          schema:
            type: integer
            maximum: 50
            minimum: 1
            description: 获取数量/Number of reels to fetch
            default: 12
            title: First
        - name: after
          in: query
          description: >-
            分页游标，首次请求不传，从上一次响应的 page_info.end_cursor 获取/Pagination cursor, omit
            for first request, get from previous response page_info.end_cursor
          required: false
          schema:
            type: string
            description: >-
              分页游标，首次请求不传，从上一次响应的 page_info.end_cursor 获取/Pagination cursor,
              omit for first request, get from previous response
              page_info.end_cursor
            title: After
      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: jIgpoch7xNZbAraobXF_z
                schemeIds:
                  - HTTPBearer
            required: true
            use:
              id: jIgpoch7xNZbAraobXF_z
            scopes:
              jIgpoch7xNZbAraobXF_z:
                HTTPBearer: []
      x-apifox-folder: Instagram-V3-API
      x-apifox-status: released
      x-run-in-apifox: https://app.apifox.com/web/project/4705614/apis/api-419083068-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: []

```