KonbiniAPI

The YouTube API for products and pipelines.

Retrieve supported public YouTube data — videos, channels and their tabs, comments, playlists, posts, transcripts, stream URLs, and search — through REST endpoints that return one consistent response model.

  • 17 supported endpoints
  • Public data only
  • Fetched at request time
GET/v1/youtube/videos/{videoId}200OK
{
  "type": "Video",
  "name": "Planetary Defenders: This Is Not an Exercise",
  "published": "2026-10-14T15:05:17.000Z",
  "duration": 1215,
  "viewCount": 563991,
  "likeCount": 10246,
  "attributedTo": {
    "preferredUsername": "@NASA",
    "isVerified": true,
    "followerCount": 15100000
  }
}

What you can pull from YouTube.

On YouTube the channel is the unit, not the person behind it, and the endpoints follow the channel page tab by tab: videos, Shorts, streams, playlists, and posts each have their own feed. Channels are addressed by handle, the name in the channel URL, or by the channel id from an earlier response, which returns faster.

A video detail carries exact view and like counts, keywords, and the languages it has captions in. Listings show the rounded figures YouTube itself displays, and each endpoint says which it returns. Transcripts are a separate call in WebVTT, and the download endpoint returns every rendition YouTube serves rather than one file.

Every response uses the same ActivityStreams 2.0-based model as the other supported platforms, so a YouTube integration reuses the parsing you already wrote. Fields specific to YouTube stay as documented first-class fields rather than being flattened away.

YouTube data
  • Channel profiles and About details
  • Video, Shorts, stream, playlist, and post tabs
  • Single videos with captions listed
  • Comments and reply threads
  • Transcripts in WebVTT and stream URLs
  • Search, tag feeds, and search suggestions

All 17 YouTube endpoints.

Grouped by what they return. Every one has its parameter contract, a request you can copy, and an example response.

Profiles

2

The channel record, and its About panel with the exact lifetime view count, creation date, and country.

Feeds

5

The channel page tab by tab: uploads, Shorts, streams, playlists, and posts, each its own feed.

Posts

5

One video, playlist, or post by id, plus a video’s WebVTT transcript and its downloadable renditions.

Comments

2

Top-level comments on a video, and the replies under any one of them.

Discovery

3

Where a run starts without an id: keyword search, the videos under a tag, and YouTube’s own search-box suggestions.

How the calls fit together.

Few YouTube jobs are a single request. Most are two or three chained, each call keyed by an id the one before it returned.

Vet a channel

Read the channel for its size, the About panel for its exact lifetime views and age, then its latest uploads.

  1. 1Get channel/v1/youtube/channels/{channel}
  2. 2Get channel about page/v1/youtube/channels/{channel}/about
  3. 3Get channel videos/v1/youtube/channels/{channel}/videos

Turn a video into text

Read the video to see which caption languages exist, then fetch the transcript in the one you need.

  1. 1Get video/v1/youtube/videos/{videoId}
  2. 2Get video transcript/v1/youtube/videos/{videoId}/transcript

Read the reaction to a video

Page the top-level comments, then open the reply thread under the ones that started a conversation.

  1. 1Get video comments/v1/youtube/videos/{videoId}/comments
  2. 2Get comment replies/v1/youtube/videos/{videoId}/comments/{commentId}/replies

What shapes your YouTube integration.

Page sizes, ordering, and what the platform itself withholds — the details that decide how you build, settled before you write a line of code.

01Most counts are YouTube’s rounded figures
Subscriber and video counts, and view counts on channel listings and playlists, are the rounded values YouTube displays, returned as integers (515M becomes 515000000). A video detail returns exact view and like counts, the About panel an exact lifetime view count, and search an exact view count.
02Channels take a handle, and optionally an id
Every channel endpoint takes the handle from the channel URL, with or without the @. If you already have the channel id, pass it too: it is used instead of the handle and returns faster.
03Stream URLs come in parts above 360p
The download endpoint returns every rendition YouTube serves. Complete files with audio only go up to 360p; above that, combine a video rendition with an audio one. URLs expire after a few hours.
04There is no trending chart
YouTube has no public trending chart. Sorting search by view count within an upload window is the closest equivalent: results for a query, not a platform-wide ranking.

Build on YouTube data.

Get a free API key and call any of these endpoints in minutes. No credit card required.