YouTube API v3
The official YouTube API. It needs API keys: each key has a daily quota shared by all tasks. In search it collects videos, channels or playlists.
A parser for YouTube data and contacts
A ZennoPoster template that collects YouTube data from lists of queries and links: search results, metadata of channels, videos and playlists, comments, posts, trends, Shorts and search suggestions. It finds emails in channel descriptions and links to social networks. It downloads videos, subtitles and thumbnails. The result of each task is saved to a table.

The method is chosen in the input settings. Some tasks work through only one of them.
The method determines which fields appear in the result table.
The official YouTube API. It needs API keys: each key has a daily quota shared by all tasks. In search it collects videos, channels or playlists.
The internal API that the YouTube site itself uses. In search it collects videos only and can search by hashtag. Large runs need proxies or a delay between requests.
One run performs one task. You choose it on the first settings tab, and the input comes from a text file with a list of queries or links.
Open the task list in the documentation| Task | YouTube API | InnerTube API |
|---|---|---|
| Search and feeds | ||
| Search results | ||
| Search suggestions | ||
| Trends | ||
| Shorts | ||
| Channels | ||
| Channel metadata | ||
| Channel subscriptions | ||
| Social network links | ||
| Videos | ||
| Video metadata | ||
| Video comments | ||
| Playlists and posts | ||
| Playlist metadata | ||
| Playlist videos | ||
| Channel posts | ||
| Post comments | ||
| Downloads | ||
| Video download | ||
| Channel download | ||
| Subtitle download | ||
| Thumbnail download | ||
A separate task checks whether API keys work.
Filters and limits are set on the task tab in the input settings.
Settings are split into tabs by task. The heading of each block names the method the task works through. The interface is in Russian.

Search results through YouTube API: type of collected data, result order, publication dates, category, definition, duration and license of videos.
A topic base is usually collected in two stages: first links from search results, then detailed data for each link.
On the first settings tab, set the method, YouTube API or InnerTube API, and one task for the run.
Search queries or links to channels, videos, playlists, posts and thumbnails go into the text file of the task, one value per line.
On the task tab, choose the input source, filters and limits. The country and language of results are set on the Additional tab.
For YouTube API, add API keys. For large InnerTube API runs, turn on proxies or the delay between requests.
Test the run on a few lines first. Tables are saved to the Results folder, downloaded files to the Downloads folder.
The template runs on an ordinary PC or a server. Tasks through YouTube API need API keys, and large runs through InnerTube API need proxies.
$170 first payment
$400 one-time payment
YouTube returns at most 600 results per query. This limit cannot be bypassed. To collect more channels, videos or playlists on a topic, use several different queries.
Not directly: YouTube does not search channels by country, audience or subscriber count. First you collect links by search queries, then channel metadata. Filters apply to that metadata: subscribers, views, creation year, country.
YouTube Data API v3 keys are created in the Google developer console. The daily quota of one key covers roughly 5 search queries or the metadata of 10,000 videos or channels. The quota resets every day, and several keys raise the daily volume.
For large runs of tasks through InnerTube API. YouTube limits the request rate from one IP and may ask for a captcha. As a guide: about 50 search queries, or 500 to 1,000 videos or channels, per IP. Private IPv4 http or socks5 proxies are suitable. Without proxies, you can turn on a delay between requests.
Addresses that the channel owner wrote in the description text. The template finds them while collecting channel metadata and writes them to a separate table column. Channels with no address in the description can be left out of the report.
Intermediate results are kept in the service database of the template. Start the template for a single execution: it will try to save the data from the database and create the tables.
The template runs in ZennoBox. Issuing ZennoBox is paid once, together with the first license payment; the amount is in the license block.
The author has a single up-to-date contact: Telegram. Use only the button below and do not search for the account by nickname or avatar.