What this API does and who it is for

Youtube Search and Download covers the core data surfaces of YouTube that most applications need: search, channel metadata, video details, playlists, subtitles, comments, and direct video downloads. It is aimed at developers building tools like content aggregators, analytics dashboards, subtitle extractors, download managers, or social-media monitoring services — essentially anything that needs structured YouTube data without going through Google's official Data API quota system.

The API carries a 97% average success rate and an average latency of 3,270 ms. That latency figure is worth keeping in mind during architectural planning: responses are not instantaneous, so designs that fire requests synchronously in a user's critical path should handle that delay gracefully, either through caching, queuing, or background fetching.

Endpoint walkthrough

The API exposes 19 endpoints spanning five broad functional areas.

Search and discovery

  • GET /search — The primary search endpoint. It supports the full range of YouTube's native filters, including duration, upload date, and content type, so you can replicate most of what a user would do on YouTube's search page programmatically.
  • GET /channel/search and POST /channel/search — Scoped search within a specific channel. Useful for building a channel-level search feature or auditing a creator's back-catalogue.
  • GET /resolve — Resolves @ usernames and short links to canonical channel IDs, which is typically the first step before calling any channel-specific endpoint.

Channel data

  • GET /channel and POST /channel — Returns the video list for a channel. Both GET and POST variants exist, presumably to accommodate larger or more complex parameter payloads.
  • GET /channel/about — Returns extended channel metadata from the channel's About page: description, contact info, stats.
  • GET /channel/shorts and POST /channel/shorts — Fetches a channel's Shorts content separately from long-form videos.
  • GET /channel/live — Lists active or recent live streams from a channel.
  • GET /channel/community — Returns community posts, which are often overlooked but valuable for monitoring creator announcements.
  • GET /channel/playlists — Returns all playlists published by a channel.

Video data

  • GET /video — Core video info endpoint. Pass a video ID, get back metadata: title, description, view count, duration, and similar fields.
  • GET /video/related — Returns videos YouTube considers related to a given video — useful for building recommendation-adjacent features.
  • GET /video/comments — Fetches a video's comment list with pagination. The provider notes that the first response includes sortTopNext and sortNewestNext fields; pass the relevant value to the next parameter to navigate sorted comment pages.
  • GET /video/download — Retrieves a downloadable stream for a video by its ID. Check the legal terms for your jurisdiction and use case before relying on this endpoint.

Subtitles

  • GET /video/subtitles/list — Returns available subtitle tracks in ISO language format, so you know what's on offer before fetching.
  • GET /video/subtitles — Fetches the actual subtitle data, supporting both manually added captions and auto-generated tracks in multiple formats.

Trending and playlists

  • GET /playlist — Returns the full video list for any playlist by ID.

Pagination is supported across all list-based endpoints, which is essential for channels or playlists with large content libraries.

Pricing breakdown

The API uses a freemium model with four tiers.

Plan Price Request allowance Rate limit
BASIC $0 / month 500 per day Not specified
PRO $5 / month 500,000 per month 50 / second
ULTRA (recommended) $12 / month 50,000,000 per month Not specified
MEGA $25 / month Unlimited per month Not specified

The BASIC tier's 500 daily requests (~15,000/month) is genuinely useful for prototyping and low-volume personal projects. Once traffic picks up, PRO at $5/month offers 500,000 monthly requests — reasonable for small production apps. The jump to ULTRA at $12/month is significant in raw quota (50 million requests/month), making it the right choice for high-throughput applications. MEGA removes the quota ceiling entirely at $25/month, with a custom plan option available for requirements that fall outside these tiers (contact details on the provider's Telegram).

The only rate limit explicitly published is 50 requests per second on the PRO plan. If throughput ceiling matters to your system design, clarify rate limits for ULTRA and MEGA before committing.

Practical use cases

Subtitle extraction and translation pipelines — The combination of /video/subtitles/list and /video/subtitles gives you a clean two-step workflow: enumerate available languages, then pull the specific track you need in your preferred format. This is a common need for accessibility tooling, translation services, and content repurposing workflows.

Channel monitoring and analytics — Using /channel/about, /channel, /channel/live, and /channel/community together, you can build a near-complete picture of a creator's activity. Pair with comment polling via /video/comments for sentiment analysis.

Content aggregation — The /search endpoint's filter support means you can replicate granular YouTube searches (e.g., videos uploaded this week under 4 minutes on a specific topic) and surface results in your own interface.

Download tooling — The /video/download endpoint enables video download features. Ensure your application's use case aligns with YouTube's terms of service and the copyright laws applicable to your users.

Limitations and things to check before integrating

  • Latency: At an average of 3,270 ms per request, this API is not suited for real-time interactive queries without caching. Build a cache layer for any data that doesn't need to be fresh on every render.
  • Rate limits: Only the PRO tier's rate limit (50 req/s) is published. If you anticipate burst traffic, confirm the limits for your tier before launch.
  • Download legality: The /video/download endpoint surfaces downloadable content. Verify this is appropriate for your use case before shipping.
  • Support channel: The provider's primary contact channel is Telegram (https://t.me/pony4boy). If your organization requires formal SLA documentation or enterprise support contracts, factor that into your evaluation.
  • No official YouTube affiliation: This is a third-party API. While the success rate is high, factor in the possibility of breakage when YouTube changes its internal structure.

Getting started

The API is listed on a marketplace (given the subscriber and pricing data), so the integration path follows the standard pattern: subscribe to a plan, grab your API key, and start calling endpoints. Begin on the BASIC plan to verify that the data shapes and latency work for your use case. For endpoint discovery, start with /resolve to convert a channel handle into an ID, then /channel to pull video listings, and /video on specific IDs for detail pages. Once you have validated the integration, projecting your monthly request volume against the pricing table above will tell you which paid tier to land on.