# 批量获取视频的最高画质播放链接/Batch get the highest quality play URL of videos

## OpenAPI Specification

```yaml
openapi: 3.0.1
info:
  title: ''
  description: ''
  version: 1.0.0
paths:
  /api/v1/douyin/app/v3/fetch_multi_video_high_quality_play_url:
    post:
      summary: 批量获取视频的最高画质播放链接/Batch get the highest quality play URL of videos
      deprecated: false
      description: >-
        # [中文]

        ### 用途:

        - 此接口目前优惠活动价为$0.25，活动结束后恢复原价$0.5。不足50个视频按50个视频收费。

        - 批量获取视频的最高画质(原始上传画质)播放链接

        - 该接口会返回最高画质的播放链接，原始上传画质是指用户上传视频时的画质，通常最高画质视频无压缩码率并且文件头包含元数据。

        - 最高画质的视频链接无法从抖音APP或网页版直接获取，需要通过此接口获取。

        - 此接口非常适合用于批量获取高清无水印视频链接，适用于需要高质量视频的场景，如视频编辑、存档、训练模型等。

        - 使用并发请求，提高批量获取效率。

        - 最多支持50个视频ID。

        ### 参数:

        - aweme_ids: 作品id列表，用逗号分隔，例如: "123,456,789"，最多50个。

        ### 返回:

        - total: 总数

        - success_count: 成功数量

        - failed_count: 失败数量

        - videos: 视频列表，每个视频包含以下字段：
            - video_id: 作品id
            - original_video_url: 最高画质(原始上传画质)播放链接
            - file_size: 文件大小（字节）
            - file_size_in_mb: 文件大小（MB）
            - content_type: 内容类型
            - success: 是否成功
            - error: 错误信息（如果失败）
        ### 备注:

        - 由于数量较多，处理时间可能会稍长，请增加等待时间。


        # [English]

        ### Purpose:

        - This interface is currently on sale for $0.25, and will return to the
        original price of $0.5 after the event ends. If there are less than 50
        videos, they will be charged as 50 videos.

        - Batch get the highest quality (original upload quality) play URL of
        videos

        - This interface will return the highest quality play URL, the original
        upload quality refers to the quality of the video when the user uploads
        it, usually the highest quality video has an uncompressed bitrate and
        the file header contains metadata.

        - The highest quality video link cannot be obtained directly from the
        Douyin APP or web version, and must be obtained through this interface.

        - This interface is very suitable for batch obtaining high-definition,
        watermark-free video links, suitable for scenarios that require
        high-quality videos, such as video editing, archiving, training models,
        etc.

        - Use concurrent requests to improve batch acquisition efficiency.

        - Support up to 50 video IDs.

        ### Parameters:

        - aweme_ids: Video id list, separated by commas, for example:
        "123,456,789", up to 50.

        ### Return:

        - total: Total count

        - success_count: Success count

        - failed_count: Failed count

        - videos: Video list, each video contains the following fields:
            - video_id: Video id
            - original_video_url: Highest quality (original upload quality) play URL
            - file_size: File size (bytes)
            - file_size_in_mb: File size (MB)
            - content_type: Content type
            - success: Whether successful
            - error: Error message (if failed)
        ### Note:

        - Due to the large number, the processing time may be slightly longer,
        please increase the waiting time.

        # [示例/Example]

        aweme_ids =
        "7512756548356492544,7448118827402972455,7126745726494821640"
      operationId: >-
        fetch_multi_video_high_quality_play_url_api_v1_douyin_app_v3_fetch_multi_video_high_quality_play_url_post
      tags:
        - Douyin-App-V3-API
        - Douyin-App-V3-API
      parameters: []
      requestBody:
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/FetchMultiVideoHighQualityPlayUrlRequest'
      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: dJM2CQxjsracNK_rzdCGh
                schemeIds:
                  - HTTPBearer
            required: true
            use:
              id: dJM2CQxjsracNK_rzdCGh
            scopes:
              dJM2CQxjsracNK_rzdCGh:
                HTTPBearer: []
      x-apifox-folder: Douyin-App-V3-API
      x-apifox-status: released
      x-run-in-apifox: https://app.apifox.com/web/project/4705614/apis/api-360401425-run
components:
  schemas:
    FetchMultiVideoHighQualityPlayUrlRequest:
      properties:
        aweme_ids:
          type: string
          title: Aweme Ids
          description: 作品id列表，用逗号分隔，最多50个/Video id list, separated by commas, up to 50
          default: 7512756548356492544,7448118827402972455,7126745726494821640
        region:
          anyOf:
            - type: string
            - type: 'null'
          title: Region
          description: >-
            可选，请求出口地区(ISO 国家代码，如 CN/US/HK)。抖音根据请求 IP 返回对应区域 CDN，国内用户传 'CN' 可获得国内
            CDN 链接以加快下载速度 / Optional, ISO country code (e.g. CN). Pass 'CN' for
            users in mainland China to get China-region CDN URLs for faster
            download.
          examples:
            - CN
      type: object
      title: FetchMultiVideoHighQualityPlayUrlRequest
      x-apifox-orders:
        - aweme_ids
        - region
      x-apifox-ignore-properties: []
      x-apifox-folder: ''
    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: []

```