Scrape YouTube
Search Results
Fetch paginated YouTube search results at scale, with video IDs, titles, channels, durations, view counts, and thumbnails in structured JSON.
- 500 free API credits included
- No payment card required
- Failed requests cost 0 credits
A simpler way to collect YouTube search results.
Get video IDs, titles, channels, durations, view counts, and thumbnails in one response.
Multiple result types
Search for videos, channels, playlists, or movies. Leave the type open to search across them.
Ranked results
Keep YouTube's relevance order, or sort by newest, most viewed, or highest rated.
Built-in filters
See results ranked for a specific country. Narrow them by upload date, duration, HD, 4K, subtitles, or live video.
No daily search cap
Keep searching throughout the day without waiting for a quota reset. Successful requests use your monthly credits.
Test it live.
See the result.
Choose a sample video, set the format, and run the endpoint without an account.
Current public data
Use Run to fetch a live, normalized response from the Tapline API.
Simple, Transparent Pricing
Start free. No card required. No charge for failed requests.
Free
Try the API with real data
Starter
Side projects and prototypes
Growth
Best for production workloads
Pro
Pricing engines and data platforms
More than 4,000,000 credits a month?
Annual contracts, higher concurrency, or an endpoint Tapline has not built yet. Send the workload and you get a price back.
Questions before you ship.
Sign up to get 500 free API credits with no card required, then create an API key in the dashboard. Send it in the X-API-Key header and you can make your first request in under a minute.
One HTTP call to one endpoint. Each request costs 2 credits, except channel info at 3, regardless of how many rows it returns. A comments page carrying 20 threads is still one request.
Yes. Your plan has one credit pool shared across every live Tapline API.
Search, comments, comment replies, and channel videos return one full page per call plus a pagination.next_cursor; send that back to get the next page. There is no limit parameter, so page size is fixed. A comments page usually carries 20 threads and a channel videos page 30 items. Playlists are the one endpoint that takes a limit, from 1 to 100 entries with a default of 50. Metadata, transcript, subtitle tracks, formats, heatmap, and channel info are single-record endpoints.
Yes. Each comments response carries pagination.next_cursor. Send it back as the cursor parameter to get the next page and repeat until next_cursor is null. Sort by new to walk the whole comment section; sorting by top follows YouTube ranked order and stops short of the full set on heavily commented videos, which the response marks as completion: depth_limit. Replies have their own endpoint: take replies_cursor from a thread and page it the same way until it runs out. Every page is one request at 2 credits.
No. Credits are charged only when a call reaches its target and returns data.
Calls return the current state at request time. Identical requests within a short window may be served from a brief cache.
No. Tapline is independent. Data is sourced from publicly visible YouTube pages.
No. Unlike the YouTube Data API, Tapline does not reset a daily quota. Requests draw from your plan's monthly credit pool. Rate and concurrency limits still apply, and failed requests use no credits.