What is YouTube InnerTube API and How does it work?

What Can Be Done with the Innertube API

Below is a detailed list of data categories and capabilities available through YouTube’s internal Innertube API. These endpoints provide structured JSON responses depending on the type of request and client.

Technical Notes

• Each data type is usually fetched from a specific endpoint (e.g., /youtubei/v1/player, /youtubei/v1/browse).
• Responses are deeply nested JSON structures typically inside renderer or runs arrays.
• Some data use “continuation” tokens for pagination.
• Different clientName values (e.g., WEB, ANDROID, TVHTML5) can return different response formats or fields for the same video or channel.

Known Innertube Clients and ClientVersions

Below are known client identifiers used by YouTube's Innertube API. Each represents a device or application type and tells YouTube which interface is making the request.

Additional information

Typical clientVersion format is a date-based build identifier:

2.YYYYMMDD.00.00  →  e.g. 2.20241010.00.00

Example JSON context commonly sent with Innertube requests:

{
  "context": {
    "client": {
      "clientName": "ANDROID",
      "clientVersion": "19.26.35",
      "androidSdkVersion": 30,
      "hl": "en",
      "gl": "US"
    }
  }
}

• Changing the clientName can cause endpoints to return different fields or formats (e.g., web vs. android responses).
• ANDROID responses often return playback URLs with fewer signature protections.
• WEB responses frequently include signatureCipher items that require additional decoding.
• TVHTML5 responses can expose higher-resolution streams (e.g., 4K) more readily.