# 获取用户粉丝列表/Get user followers list

## OpenAPI Specification

```yaml
openapi: 3.0.1
info:
  title: ''
  description: ''
  version: 1.0.0
paths:
  /api/v1/instagram/v3/get_user_followers:
    get:
      summary: 获取用户粉丝列表/Get user followers list
      deprecated: false
      description: >-
        # [中文]

        ### 用途:

        - 获取Instagram用户的粉丝列表

        - 返回关注该用户的所有账号信息

        - 支持分页获取

        ### 参数:

        - username: Instagram用户名（必填）

        - count: 每次获取数量（默认12，最大100）

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

        ### 返回:

        - `data.users`: 粉丝用户列表
            - `pk`: 用户ID
            - `username`: 用户名
            - `full_name`: 全名
            - `is_private`: 是否私密账号
            - `is_verified`: 是否认证
            - `profile_pic_url`: 头像URL
        - `data.next_max_id`: 下一页分页游标（传给下次请求的max_id参数）

        - `data.big_list`: 是否有更多数据

        - `data.page_size`: 每页数量

        - `data.status`: 状态

        ### 分页使用方法:

        1. 首次请求：只传 `username` 和 `count` 参数

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

        3. 下次请求：传入 `username`、`count` 和 `max_id` (使用上次的next_max_id)

        4. 重复步骤 2-3 直到响应中没有 `next_max_id` 字段

        ### 价格:

        - 0.008 USD/请求


        # [English]

        ### Purpose:

        - Get Instagram user's followers list

        - Returns all accounts that follow this user

        - Support pagination

        ### Parameters:

        - username: Instagram username (required)

        - count: Number of users to fetch per request (default 12, max 100)

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

        ### Return:

        - `data.users`: Followers user list
            - `pk`: User ID
            - `username`: Username
            - `full_name`: Full name
            - `is_private`: Whether private account
            - `is_verified`: Whether verified
            - `profile_pic_url`: Profile picture URL
        - `data.next_max_id`: Next page cursor (use as max_id in next request)

        - `data.big_list`: Whether has more data

        - `data.page_size`: Page size

        - `data.status`: Status

        ### Pagination usage:

        1. First request: Only pass `username` and `count` parameters

        2. Get `data.next_max_id` from response

        3. Next request: Pass `username`, `count`, and `max_id` (use next_max_id
        from previous)

        4. Repeat steps 2-3 until response has no `next_max_id` field

        ### Price:

        - 0.008 USD/request


        ### 示例/Example

        username = "instagram"

        count = 12
      operationId: get_user_followers_api_v1_instagram_v3_get_user_followers_get
      tags:
        - Instagram-V3-API
        - Instagram-V3-API
      parameters:
        - name: username
          in: query
          description: 用户名/Username
          required: true
          example: instagram
          schema:
            type: string
            description: 用户名/Username
            title: Username
        - name: count
          in: query
          description: 每次获取数量/Number of users to fetch per request
          required: false
          schema:
            type: integer
            maximum: 100
            minimum: 1
            description: 每次获取数量/Number of users to fetch per request
            default: 12
            title: Count
        - name: max_id
          in: query
          description: >-
            分页游标，首次请求不传，从上一次响应的 next_max_id 获取/Pagination cursor, omit for first
            request, get from previous response next_max_id
          required: false
          schema:
            type: string
            description: >-
              分页游标，首次请求不传，从上一次响应的 next_max_id 获取/Pagination cursor, omit for
              first request, get from previous response next_max_id
            title: Max 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: VTwEDKLscrmgJIUsqvPuX
                schemeIds:
                  - HTTPBearer
            required: true
            use:
              id: VTwEDKLscrmgJIUsqvPuX
            scopes:
              VTwEDKLscrmgJIUsqvPuX:
                HTTPBearer: []
      x-apifox-folder: Instagram-V3-API
      x-apifox-status: released
      x-run-in-apifox: https://app.apifox.com/web/project/4705614/apis/api-419083078-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: []

```