YouTube Video Details Scraper
One YouTube video's metadata as typed JSON: title, channel, description, views, likes, duration, tags, categories, thumbnails and upload date. Pass a watch URL or video ID. 1 credit per call. No YouTube login.
Free API key · 1 credit per video · failed calls free
// GET /api/v2/youtube-video-details/?urls=https://www.youtube.com/watch?v=dQw4w9WgXcQ · sample from the catalog { "success": true, "data": { "urls": "https://www.youtube.com/watch?v=dQw4w9WgXcQ", "page": 1, "page_size": 10, "videos": [ { "video_id": "dQw4w9WgXcQ", "url": "https://www.youtube.com/watch?v=dQw4w9WgXcQ", "title": "Never Gonna Give You Up", "channel_name": "Rick Astley", "channel_id": "UCuAXFkgsw1L7xaCfnd5JJOw", "description": "Official music video...", "view_count": 1500000000, "like_count": 18000000, "duration_seconds": 213, "upload_date": "2009-10-25", "tags": [ "music", "rick astley" ], "categories": [ "Music" ], "thumbnails": [ { "url": "https://i.ytimg.com/vi/dQw4w9WgXcQ/maxresdefault.jpg" } ] } ], "next_cursor": null } }
| field | value | type | Has a value✓ |
|---|
Scrapier's YouTube Video Details Scraper, a YouTube metadata scraper, returns one video's details as JSON from a watch URL or video ID: title, channel_name, view_count, like_count, duration_seconds, tags and upload_date. It costs 1 credit per successful call. No YouTube login.
YouTube Video Details Scraper extracts one video per call: video ID, title, channel name and ID, description, view count, like count, duration in seconds, upload date, tags, categories and thumbnails. As a YouTube metadata scraper it returns structured JSON, ready to pass directly to an LLM, index into a vector store or feed a video-analytics pipeline. It is one of 17 YouTube endpoints on the same API key used by 12,000+ developers. Transcripts and subtitles are not in this response; use the YouTube subtitles endpoint on the same key for those.
What data can I extract with YouTube Video Details Scraper?
Using this YouTube Video Details Scraper, you can extract the following data from public YouTube videos:
Want the exact field names? See the example output.
Try YouTube Video Details Scraper Live
Press Run to see the catalog sample. Add your API key and it runs a real call to the Scrapier API from your browser. The key is sent only to proxy.scrapier.io and never stored.
+ Run live with your API key
How to use YouTube Video Details Scraper
Hand it to your AI assistant, or run it yourself in five steps.
Copy to your AI assistant
Paste this into ChatGPT, Claude or Cursor and it knows how to call the scraper.
Use the Scrapier YouTube Video Details Scraper to get public YouTube videos. Endpoint: GET https://proxy.scrapier.io/api/v2/youtube-video-details/?urls={urls} with header "X-API-Key: YOUR_API_KEY" and a 210-second timeout. Send one value per call in urls; for a list, make one call per value, at most 3 in parallel. It returns JSON under data.videos: video_id, url, title, channel_name, channel_id, description, view_count, like_count, duration_seconds, upload_date, tags, categories. Each successful call costs 1 credit; failed calls are free. If you support MCP, run: claude mcp add -t http scrapier https://mcp.scrapier.io/mcp --header "X-API-Key: YOUR_API_KEY" and call run_scrape with endpoint "youtube-video-details" (find it with search_endpoints).Use this scraper from ChatGPT, Claude or Cursor. Point your assistant at Scrapier and it reads YouTube videos on its own: no glue code, no scraping logic in your prompts.
Run it yourself
- Get your free Scrapier API keySign up at app.scrapier.io; the free tier lets you try it first.
- Open YouTube Video Details Scraper in the catalogIt lives under Scrapers / YouTube.
- Enter the video URL or IDFor example
https://www.youtube.com/watch?v=dQw4w9WgXcQor the bare video ID inurls. - Send your API requestOne GET with your key in the
X-API-Keyheader, or onerun_scrapecall from your agent. Set a 210-second client timeout. - Save your resultsThe video comes back as JSON in
data.videos: store it as is, or pull the fields you need into a table in a few lines.
How to scale to bulk YouTube videos
urls takes one video per call, so for a list you loop: one request per video. Run up to 3 requests in parallel per API key; above that the API answers 429 with a Retry-After header, and throttled calls cost nothing. Each video is 1 credit and failed calls are free, so 1,000 videos cost 1,000 credits, inside the Hobby plan's 15,000. To get video URLs in bulk, run the YouTube Channel Video Scraper or the hashtag endpoint first and loop over their results.
Features
YouTube Video Details Scraper fetches clean, structured metadata for a single video at low cost. It suits video analytics, content audits, competitor tracking, dataset building and any workflow that needs reliable video facts from a URL.
- Identity
video_id,title,urlandchannel_name - Reach
view_countandlike_countas numbers - Length
duration_secondsas a number of seconds - Context
description,tagsandcategories - Dates
upload_dateandscraped_at - Media
thumbnailslist with image URLs
Proxies, retries and parsing run on Scrapier's side, so you send one request and get JSON back, at 1 credit per video and 0 credits for a failed call.
Use cases
- Video analyst feeds a list of 500 video URLs through the scraper and stores title, views, likes and tags to compare formats.
- Brand monitor checks
view_countandlike_counton sponsored videos every week to report reach to a client. - Dataset builder collects titles, descriptions, tags and categories into a table, one row per video, for training and evaluation sets.
- SEO team reads the
tagsanddescriptionof top-ranking videos to study how competitors describe a topic. - AI engineer gives an agent a tool that takes a pasted YouTube link, calls
youtube-video-detailsand answers fromdata.videoswith itsscraped_attime.
Running these from an agent? Use the MCP integration and let Claude or Cursor call the scraper directly.
Why choose this Scraper API?
Each call reads the video at call time, and the response carries scraped_at, so you know how fresh the view and like counts are.
urls accepts a watch URL or a video ID (aliases url, video_url, video_urls and video_id), and the response echoes it in input_url so you can match results to your list.
Video details, comments, subtitles and channel endpoints share the same key and response envelope, so going from a video to its comments is a change of endpoint, not of code.
Input
The scraper takes one YouTube video per call in urls: a watch URL or a video ID. It is required on the first call and ignored once you pass a cursor. Send parameters in the query string (GET) or as a JSON body (POST).
| Name | Type | Required | Default | Description |
|---|---|---|---|---|
urls | string | Yes | — | A YouTube watch URL or video ID. One per call. Required on the first call; ignored when cursor is supplied. Aliases: url, video_url, video_urls, video_id |
cursor | string | No | — | Pass back data.next_cursor from the previous response to get the next page; null means the last page |
use_proxy | boolean | No | true | Route through Scrapier's residential proxy pool. Leave as is |
raw_data | boolean | No | false | Return YouTube's raw upstream payload under raw_responses instead of the formatted items |
One video per call: to look up ten videos, make ten calls. Booleans are the strings true or false.
Example input
{
"urls": "https://www.youtube.com/watch?v=dQw4w9WgXcQ",
"use_proxy": "true",
"raw_data": "false"
}Error codes
| Status | Meaning | Billed | Fix |
|---|---|---|---|
| 200 | Video data returned in data.videos | Yes | — |
| 400 | Bad or missing input | No | Check urls: one value per call |
| 401 | X-API-Key header missing | No | Add the header |
| 402 | Out of credits (body has balance) | No | Top up; retrying will not help |
| 403 | Invalid or revoked API key | No | Check the key in your dashboard |
| 429 | Throttled | No | Wait Retry-After seconds, then retry |
| 5xx | Upstream failure or timeout | No | Retry with backoff; set a 210 s client timeout |
From the error reference. Any non-2xx response costs 0 credits.
Output
Typed JSON with the same schema on every call. One call returns a list with one video under videos, with 15 fields, inside the standard data envelope. Field names stay the same on every call. Set raw_data to true if you want YouTube's raw payload instead.
Example output
{
"success": true,
"data": {
"urls": "https://www.youtube.com/watch?v=dQw4w9WgXcQ",
"page": 1,
"page_size": 10,
"videos": [
{
"video_id": "dQw4w9WgXcQ",
"url": "https://www.youtube.com/watch?v=dQw4w9WgXcQ",
"title": "Never Gonna Give You Up",
"channel_name": "Rick Astley",
"channel_id": "UCuAXFkgsw1L7xaCfnd5JJOw",
"description": "Official music video...",
"view_count": 1500000000,
"like_count": 18000000,
"duration_seconds": 213,
"upload_date": "2009-10-25",
"tags": [
"music",
"rick astley"
],
"categories": [
"Music"
],
"thumbnails": [
{
"url": "https://i.ytimg.com/vi/dQw4w9WgXcQ/maxresdefault.jpg"
}
],
"scraped_at": "2026-12-01T12:00:00.000Z",
"input_url": "https://www.youtube.com/watch?v=dQw4w9WgXcQ"
}
],
"next_cursor": null
}
}The catalog's sample response for urls=https://www.youtube.com/watch?v=dQw4w9WgXcQ, labelled as a sample: live calls return the account's current values.
Identity
| Field | Type | Example | Description |
|---|---|---|---|
videos.video_id | string | "dQw4w9WgXcQ" | YouTube video ID |
videos.url | string | "https://www.youtube.com/watch?v=dQw4w9WgXcQ" | Watch URL of the video |
videos.title | string | "Never Gonna Give You Up" | Title of the video |
videos.channel_name | string | "Rick Astley" | Name of the uploading channel |
videos.channel_id | string | "UCuAXFkgsw1L7xaCfnd5JJOw" | UC channel ID of the uploader |
Reach and length
| Field | Type | Example | Description |
|---|---|---|---|
videos.view_count | integer | 1500000000 | Views as a number |
videos.like_count | integer | 18000000 | Likes as a number |
videos.duration_seconds | integer | 213 | Length in seconds |
videos.upload_date | string | "2009-10-25" | Upload date (YYYY-MM-DD) |
Content
| Field | Type | Example | Description |
|---|---|---|---|
videos.description | string | "Official music video..." | Description text of the video |
videos.tags | array | 2 items | List of tags |
videos.categories | array | 1 items | List of categories, such as Music |
videos.thumbnails | array | 1 items | List of thumbnails with image URLs |
Input and timestamp
| Field | Type | Example | Description |
|---|---|---|---|
videos.input_url | string | "https://www.youtube.com/watch?v=dQw4w9WgXcQ" | The video input you sent |
videos.scraped_at | string | "2026-12-01T12:00:00.000Z" | When Scrapier read the video (ISO 8601, UTC) |
Response envelope and paging
| Field | Type | Example | Description |
|---|---|---|---|
success | boolean | true | true on every 200 response |
data.urls | string | "https://www.youtube.com/watch?v=dQw4w9WgXcQ" | Your video input, echoed back |
data.page | integer | 1 | Page number of this response |
data.page_size | integer | 10 | Videos per page |
data.next_cursor | null | null | null in the catalog sample: a video is a single lookup |
How does it work?
Scrapier sends each request through its residential proxy pool (use_proxy, on by default), so you never manage IPs or proxy accounts.
Retries and parsing of YouTube's pages and responses happen on Scrapier's side. You send one HTTP request and get typed JSON back.
Only publicly visible data is returned: what any visitor sees without signing in. No YouTube account, cookie or Google API key is used for this endpoint.
The schema is stable. When YouTube changes, Scrapier updates the scraper; the field names under videos stay the same.
How do you integrate YouTube Video Details Scraper into your stack?
It works with what you already use: any HTTP client, AI agents over MCP, and no-code automation tools. Code samples for cURL, Python and Node.js are on the API tab.
MCP integration for AI agents
This registers the Scrapier MCP server, whose tools reach every Scrapier scraper, including youtube-video-details: the agent finds it with search_endpoints and calls it with run_scrape. Works with Claude Code, Cursor and Windsurf. MCP calls are billed like REST: 1 credit per successful call. Full MCP setup →
No-code tools (n8n, Make, LangChain)
Use the HTTP Request node with your Scrapier API key in an X-API-Key header and point it at /api/v2/youtube-video-details/ with a urls query parameter. Map data.videos into the next node.
Add an HTTP "Make a request" module with the same header and URL, and parse the response as JSON. Map title and view_count straight into Sheets, Airtable or your CRM.
Wrap the endpoint in a requests-based tool, or load the Scrapier MCP server through LangChain's MCP adapters so the agent finds youtube-video-details with search_endpoints itself.
Pricing and Rate Limits
One YouTube video costs 1 credit, so 1,000 videos cost 1,000 credits: $1.58 on the Pro plan. Failed and empty calls are not billed. Run up to 3 requests in parallel per key; above that the API answers 429 with a Retry-After header.
| Plan | Monthly price | Credits | Videos included | Per 1,000 videos |
|---|---|---|---|---|
| Hobby | $29 | 15,000 | 15,000 | $1.93 |
| Pro | $79 | 50,000 | 50,000 | $1.58 |
| Scale | $299 | 250,000 | 250,000 | $1.20 |
| Enterprise | Custom volume and terms | |||
Prices from the live billing page. See all plans and limits.
Call cost and timing
How we measure this
Credit cost, pagination and the sample come from the live catalog (GET /api/v2/endpoints, /youtube-video-details/, checked 9 Nov 2026). Concurrency and timeout guidance come from the rate limits page of the docs. Scrapier does not publish latency or success-rate figures for this endpoint, so none are shown here.
YouTube Video Details Scraper vs the Official YouTube API
| Feature | Scrapier video scraper | Official YouTube API |
|---|---|---|
| Access needed | One Scrapier API key | A Google Cloud project, an API key and a daily quota |
| Which videos | Any public video, by URL or ID | Videos by ID through the videos resource |
| Fields returned | 15 video fields, including views, likes, tags and thumbnails | Depends on the parts you request |
| Rate limits | Up to 3 parallel requests per key; 429 with Retry-After | Daily quota units set per Google Cloud project |
| Setup | Sign up, copy a key, send a request | Create a project, enable the API, create credentials |
| Cost | 1 credit per video, from $1.20 per 1,000 videos | Free within quota; more needs a quota extension request |
The official YouTube Data API is the better choice when you need data about videos on your own channel, or must follow Google's API terms for a published app.
Is it legal to scrape YouTube data?
Scraping publicly available YouTube data is generally lawful in many countries, but the answer depends on what you collect, where you are and how you use it. In the US, hiQ Labs v. LinkedIn is the case most often cited on public-data scraping. Scrapier returns only data any visitor can see without logging in. Under GDPR and similar laws, collecting public data can be permissible, but how you store and use personal data, such as names or comment text, must still comply with local data-protection rules, and YouTube's terms apply. Consult legal counsel if your use case involves bulk storage of personal data. This is not legal advice; see our Terms of Use.
Frequently asked questions
What fields does YouTube Video Details Scraper return?
The top ones are title, channel_name, view_count, like_count, duration_seconds, upload_date, tags, categories and description, plus video_id, url, thumbnails and scraped_at: 15 fields in data.videos. Each successful call costs 1 credit and needs no YouTube login.
Does it return the transcript of a video?
No. The catalog sample for this endpoint has no transcript or subtitle field. Subtitles and transcript text come from the separate YouTube subtitles endpoint, which uses the same API key and the same response envelope.
Can I look up a video by ID instead of a URL?
Yes. The urls parameter accepts a watch URL or a video ID, and also answers to the aliases url, video_url, video_urls and video_id. The response echoes your input in input_url, so you can match each record back to your list.
Can I scrape multiple YouTube videos at once?
Yes, with one call per video: urls takes a single value. Loop over your list and run up to 3 requests in parallel per API key. 1,000 videos cost 1,000 credits; failed and throttled calls are free.
Does YouTube Video Details Scraper require a YouTube account or login?
No. The YouTube Video Details Scraper uses no YouTube account or cookies: you send your Scrapier API key in the X-API-Key header and a video URL or ID, and get JSON back. Only public YouTube data is returned, and no Google API key or quota is involved.
How fast does YouTube Video Details Scraper run?
Scrapier does not publish a latency figure for this endpoint. Each call reads YouTube live, and scraped_at in the response records when. Set a client timeout of 210 seconds, as the docs recommend for every endpoint.
What happens if the input is wrong or YouTube returns nothing?
If a call fails, the API returns a non-2xx status and costs 0 credits. In code, check the status, then skip that input or retry it later. Throttled calls (429 with a Retry-After header) are free as well, so retry loops cost nothing.
Does YouTube Video Details Scraper work with Claude, ChatGPT and other AI agent tools?
Yes. Connect the Scrapier MCP server with claude mcp add -t http scrapier https://mcp.scrapier.io/mcp and your API key in an X-API-Key header; it works in Claude Code, Cursor and Windsurf. The agent finds youtube-video-details with search_endpoints and calls it with run_scrape. Any agent that can call an HTTP endpoint can use the REST API directly.
How does it compare to other YouTube scrapers?
Scrapier charges a flat 1 credit per successful call, and failed calls are free; platforms that bill compute units vary with run time and infrastructure. The same API key and MCP server reach all 199 Scrapier endpoints. Scrapier returns structured JSON for public YouTube data.
Does it return data in a format LLMs can use directly?
Yes. Every response is typed JSON with the same field names on every call: no HTML parsing and no selectors. Pass it straight to an LLM, index it into a vector store or return it from an agent tool.
What happens when YouTube changes its layout or anti-bot system?
Scrapier maintains the scraper. When YouTube changes its pages or internal responses, Scrapier updates it, and your calls keep returning the same JSON field names without changes on your end.
How much does it cost to run YouTube Video Details Scraper 1,000 times?
1,000 credits, because each call is 1 credit. That is about $1.93 on Hobby, $1.58 on Pro and $1.20 on Scale, at the plans' price per credit. Failed calls are free.
How do I use YouTube Video Details Scraper with Python?
Send a GET request with the requests library to https://proxy.scrapier.io/api/v2/youtube-video-details/ with params={"urls": "https://www.youtube.com/watch?v=dQw4w9WgXcQ"}, your key in the X-API-Key header and timeout=210. Read r.json()["data"]["videos"]: it is already JSON, so no HTML parsing is needed.
Is it legal to scrape YouTube data?
It depends on your use and your country, so this is not legal advice. Scrapier returns public YouTube data only. YouTube's terms and privacy law such as GDPR or CCPA apply to how you store and use it. Collect only what you need, and ask a lawyer about your specific case.
Your feedback
Found a bug or missing a field? Let us know. Write to support@scrapier.io and the team replies to every report.
Start Scraping YouTube Videos
Public YouTube videos as JSON, 1 credit each, from REST or MCP.