Video search monitoring
Use YouTube endpoints to turn video search monitoring into repeatable API requests with documented inputs and JSON responses.
Build creator intelligence, video research, transcript, and audience-comment workflows without maintaining YouTube scrapers.
Collect YouTube video, channel, playlist, search, transcript, and comments data through documented Crawlora API endpoints.
Endpoint families
6
Documented params
58
Examples
15
Live catalog snapshot
Active endpoints
15
Methods
GET
Required params
31
Schema refs
15
{
"platform": "YouTube",
"endpoint": "youtube-video",
"method": "GET",
"path": "/youtube/video/{id}",
"auth": "apiKey"
}Related use cases
Free tools
Showcase proof
Explore structured examples generated from public YouTube videos. See how Crawlora turns transcripts, comments, metadata, topics, and summaries into JSON for creator intelligence, RAG, content research, and monitoring workflows.
Transcript, comment, summary, topic, and metadata records for public AI videos.
Open examplesStructured public podcast and interview examples for searchable video research.
Open examplesFounder, market, and operator video examples for public business intelligence workflows.
Open examplesCreator and audience intelligence examples built from public transcripts, metadata, and comments.
Open examplesOpen the full Crawlora YouTube video intelligence showcase library.
Open examplesUse cases
Collect YouTube video, channel, playlist, search, transcript, and comments data through documented Crawlora API endpoints.
Use YouTube endpoints to turn video search monitoring into repeatable API requests with documented inputs and JSON responses.
Use YouTube endpoints to turn creator and channel research into repeatable API requests with documented inputs and JSON responses.
Use YouTube endpoints to turn transcript and comments analysis into repeatable API requests with documented inputs and JSON responses.
Managed execution
Every figure below is read from the live YouTube endpoint catalog — 15 endpoints, 58 documented request parameters, and 15 published response schemas — the same catalog Docs and Playground run against.
15 documented YouTube endpoints, grouped into 10 request families — Channel, Comments and Transcript, plus 7 more.
58 request parameters are documented across those YouTube endpoints, 31 of them required — the full input contract is public before you write any integration code.
15 of the 15 YouTube endpoints ship a recorded example response, and 15 carry a documented response schema — you can code against the real JSON before the first request.
YouTube endpoints document their error responses (400, 404, 429, 500 and 503) alongside the success schema, so a block, a rate limit, or a missing record comes back as a typed error rather than silently empty data.
15 hosted MCP tools back the YouTube endpoints, so an agent can call the same routes with the same parameters and the same JSON contract, with no custom glue.
Coverage map
/youtube/channel/{id}/videos
/youtube/comments/{id}
/youtube/transcript/{id}
/youtube/captions/{id}
/youtube/playlist/{id}
/youtube/profile/{id}
Featured endpoints
/youtube/video/{id}Returns the metadata of a YouTube video by its 11-character `id`: title, description, channel id and title, publication time, duration in seconds, and view, like and comment counts. Some fields are best-effort.
MCP tool youtube_video
/youtube/transcript/{id}Returns transcript segments for a YouTube video using YouTube's native player captions. Set `format=text`, `format=srt`, or `format=vtt` to receive plain-text output instead of the standard response envelope. Returns `404` when the video currently has no transcript/captions available in any language — this is a normal, non-retryable result, not an error condition. Returns `503` when the request is temporarily blocked or rate-limited; retrying after a short delay may succeed.
Response notes
- `404` — the video currently has no transcript/captions available in any language. This is a normal result for videos without captions (e.g. never had them, or auto-captions were never generated), not a transient failure — retrying will not help. - `503` — the request was temporarily blocked or rate-limited upstream. This is a transient condition; retrying after a short delay may succeed.
MCP tool youtube_transcript
/youtube/comments/{id}Returns one page of top-level comments for a YouTube video by its 11-character `id`. Each comment has its id, content, author `user_name` and `channel_id`, `likes_count`, `reply_count` and `published_time`. Comments with replies may include their own `continuation_token`; pass that token to `/youtube/comments/{id}/replies`. Pass the response-level `continuation_token` here for deterministic pagination. If omitted, the service discovers an initial cursor or may resume the most recently cached cursor for this video.
MCP tool youtube_comments
/youtube/searchReturns normalized YouTube search results using YouTube's InnerTube search API. Pass `continuation_token` from a previous response to retrieve the next page. Use `q` as the primary query parameter; `search_query` is accepted as an alias. `hl` and `gl` localize ranking and result context; they default to `en` and `US`. Named filters cover the public web search filters. Account-only chips such as Watched and Unwatched are not exposed.
MCP tool youtube_search
/youtube/profile/{id}Returns the profile of a YouTube channel by `id`, which can be a channel id, `@handle`, `/c` or `/user` path, bare username or full channel URL. The profile has channel id, name and URL, bio, join date, region, profile picture, links, and `stats` with `followers_count`, `videos_count` and `views_count`.
MCP tool youtube_profile
/youtube/playlist/{id}Returns a YouTube playlist by playlist id or full playlist URL: title, URL, owning channel, video count and thumbnail, plus its videos with position, title, video id, duration, channel and view count. Pass the returned `continuation_token` to page through longer playlists.
MCP tool youtube_playlist
Related APIs
Social & Creator Platforms
Turn Twitch's public channel, stream, clip, and team data into structured JSON — live status and viewer counts, top games, clips, VODs, and team rosters — as normalized JSON. Credential-free.
Social & Creator Platforms
Track creator and video activity, discover sounds and LIVE streams, and study public ad creatives through documented TikTok API routes.
Social & Creator Platforms
Turn Instagram public data into structured inputs for social listening and creator research.
Company coverage
Alphabet Inc. · GOOGL
YouTube is operated by Alphabet Inc. (GOOGL). Crawlora's SEC endpoints take the same company's CIK, so filings, financials, insider transactions and 13F holdings come from the same API key as the YouTube endpoints above.
Other Alphabet Inc. platforms in the catalog
How to scrape YouTube
YouTube holds transcripts, comments, and channel data that power research and AI pipelines. Crawlora's YouTube endpoints return them as structured JSON — including full transcripts.
A video, a channel, a video's full transcript, or its comment threads.
Pass the video or channel URL/ID to Crawlora's YouTube endpoint.
Receive title, views, likes, channel stats, the full transcript, and comment threads as clean JSON.
Pipe transcripts into LLMs and vector stores, or re-run to track views and new comments.
客户端库
为你的语言安装 YouTube 专用客户端。每个包都覆盖本页的 YouTube 端点，并使用你的 API 密钥调用 Crawlora 托管 API。
npm install @crawlora-org/youtubenpmpip install crawlora-youtubePyPIgo get github.com/Crawlora-org/crawlora-youtubepkg.go.devgem install crawlora-youtubeRubyGemsnet.crawlora:crawlora-youtubeMaven Centralcomposer require crawlora/youtubePackagistcargo add crawlora-youtubecrates.ioFAQ
Send a YouTube video or channel URL to Crawlora's YouTube endpoint and get structured JSON — title, views, likes, channel stats, full transcript, and comments — no API quota to manage. Collect public data and respect YouTube's terms.
Yes — Crawlora returns the full transcript for videos that have captions, ideal for RAG and content research. You can also try it instantly with the free YouTube Transcript Extractor at /tools/youtube-transcript-extractor.
Yes. The official YouTube Data API v3 works well but has a limited daily quota (10,000 units by default), needs OAuth or API-key setup, and doesn't return video transcripts. Crawlora's YouTube endpoints have no per-day quota to manage, use one x-api-key, and include full transcripts and comments as JSON — a practical alternative for research, RAG, and monitoring.
Collecting publicly accessible video, transcript, and comment data is generally permissible if you respect YouTube's terms of use, robots directives, rate limits, and applicable law. This is for public data you're authorized to collect.