# 获取视频流信息/Get video streams info

## OpenAPI Specification

```yaml
openapi: 3.0.1
info:
  title: ''
  description: ''
  version: 1.0.0
paths:
  /api/v1/youtube/web_v2/get_video_streams:
    get:
      summary: 获取视频流信息/Get video streams info
      deprecated: false
      description: >-
        # [中文]

        ### ⚠️ 重要说明:

        - **此接口仅返回格式信息，URL 字段为 null**

        - **必须搭配 get_signed_stream_url 接口获取播放地址**

        - 如需一次性获取所有 URL，请使用 get_video_streams_v2 接口


        ### 用途:

        - 获取YouTube视频所有清晰度的格式信息

        - 返回标准格式（音视频合并）和自适应格式（音视频分离）


        ### 参数:

        - video_id: 视频ID（推荐）

        - video_url: 完整的视频URL（可选，如果提供video_id则忽略）


        ### 返回数据包含:

        - 视频基本信息（标题、作者、时长、观看次数等）

        - formats: 标准格式流（包含音频和视频）

        - adaptive_formats: 自适应格式流（仅视频或仅音频）
          - 每个格式包含: itag、mime_type、质量标签、分辨率、比特率等
          - ⚠️ **url 字段为 null**（YouTube 需要签名解密才能获取真实播放地址）
          - has_signature 为 true 表示需要使用 get_signed_stream_url 接口
        - hls_manifest_url: HLS流地址（如果有）

        - dash_manifest_url: DASH流地址（如果有）

        - available_qualities: 所有可用的清晰度列表


        ### 使用流程（两步法）:

        1. **第一步**: 调用此接口获取所有可用格式信息（URL 为 null）

        2. **第二步**: 从返回的 formats 或 adaptive_formats 中选择需要的 itag

        3. **第三步**: 调用 get_signed_stream_url 接口，传入 video_id 和 itag，获取真实播放地址


        ### 注意事项:

        - YouTube 视频播放地址需要签名解密，原始 API 返回的 URL 字段为 null 是正常现象

        - 播放地址必须通过 get_signed_stream_url 接口单独获取

        - 高清视频（720p+）通常需要分别下载音视频流并合并


        ### 价格:

        - $0.001 USD/请求


        # [English]

        ### ⚠️ Important Notice:

        - **This endpoint ONLY returns format information, URL fields are null**

        - **MUST use get_signed_stream_url endpoint to get playback URLs**

        - For getting all URLs at once, use get_video_streams_v2 endpoint


        ### Purpose:

        - Get all quality format information for YouTube video

        - Returns standard formats (merged audio/video) and adaptive formats
        (separate audio/video)


        ### Parameters:

        - video_id: Video ID (recommended)

        - video_url: Full video URL (optional, ignored if video_id is provided)


        ### Returns:

        - Basic video info (title, author, duration, view count, etc.)

        - formats: Standard format streams (audio and video combined)

        - adaptive_formats: Adaptive format streams (video-only or audio-only)
          - Each format contains: itag, mime_type, quality label, resolution, bitrate, etc.
          - ⚠️ **url field is null** (YouTube requires signature decryption to get actual playback URL)
          - has_signature=true means need to use get_signed_stream_url endpoint
        - hls_manifest_url: HLS manifest URL (if available)

        - dash_manifest_url: DASH manifest URL (if available)

        - available_qualities: List of all available quality levels


        ### Usage Flow (Two-Step Method):

        1. **Step 1**: Call this endpoint to get all available format
        information (URLs are null)

        2. **Step 2**: Select the desired itag from returned formats or
        adaptive_formats

        3. **Step 3**: Call get_signed_stream_url endpoint with video_id and
        itag to get actual playback URL


        ### Notes:

        - YouTube video playback URLs require signature decryption, null URL
        fields in raw API response is normal

        - Playback URLs must be obtained separately via get_signed_stream_url
        endpoint

        - High-quality videos (720p+) usually require separate download and
        merge of audio/video streams


        ### Price:

        - $0.001 USD/request


        ### [示例/Example]

        #### Step 1 - 获取格式信息: video_id = "dQw4w9WgXcQ"

        #### Step 2 - 获取播放地址: use get_signed_stream_url with selected itag
      operationId: get_video_streams_api_v1_youtube_web_v2_get_video_streams_get
      tags:
        - YouTube-Web-V2-API
        - YouTube-Web-V2-API
      parameters:
        - name: video_id
          in: query
          description: 视频ID/Video ID
          required: false
          example: dQw4w9WgXcQ
          schema:
            type: string
            description: 视频ID/Video ID
            title: Video Id
        - name: video_url
          in: query
          description: 视频URL/Video URL (如果提供video_id则忽略此参数/Ignored if video_id is provided)
          required: false
          example: https://www.youtube.com/watch?v=dQw4w9WgXcQ
          schema:
            type: string
            description: >-
              视频URL/Video URL (如果提供video_id则忽略此参数/Ignored if video_id is
              provided)
            title: Video Url
      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: jIJvMoX9R639Xo9zylHEE
                schemeIds:
                  - HTTPBearer
            required: true
            use:
              id: jIJvMoX9R639Xo9zylHEE
            scopes:
              jIJvMoX9R639Xo9zylHEE:
                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-419083090-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: []

```