YouTube · Posts and media
YouTube Playlist Scraper API
- 0.15¢ per call
- $1.49 per 1,000
- Takes a playlist ID
- Errors and timeouts are not charged
On YouTube
The call
One GET, and the playlist comes back as JSON.
Your key goes in one header. 1 required parameter, and the answer is the object below it.
The full referencecurl "https://hproxy.com/api/v1/scrape/youtube/playlist?playlist_id=1234567890" \
-H "X-API-Key: hpx_your_key_here"{
"title": "Deep work",
"itemCount": 84,
"owner": { "name": "Channel name", "id": "UC..." },
"items": [
{ "position": 1, "title": "First item", "duration": 214, "id": "dQw4..." }
]
}What comes back
The YouTube playlist object.
- items[]
- Every entry in playlist order with title and duration.
- itemCount
- How many entries the playlist holds.
- owner
- Channel or account that owns the playlist.
What it takes
Parameters.
Identifier from a previous response.
How it works
Scraping YouTube playlist, in three steps.
You write one line. Proxies, anti-bot walls, rendering and parsing happen on our side.
- 1
Create a free account
Sign up and top up any amount. The balance pays for every HProxy product. - 2
Grab your API key
One key from the dashboard authenticates every scraper. - 3
Call the endpoint
Send the GET you need and read the JSON. That is the entire integration.
What people build with it
Where the YouTube playlist endpoint earns its keep.
- Mirror a YouTube playlist into your own catalogue.
- Track what gets added and removed over time.
- Build recommendations from playlist co-occurrence.
YouTube playlist questions
Answered before you ask.
Send one authenticated HTTPS request to the YouTube Playlist endpoint with a playlist ID and your HProxy API key. Pull a YouTube playlist in full: every video in playlist order with title, duration and channel, plus the playlist owner. No proxies, no headless browser and no parsing on your side. The response is ready-to-use JSON.
This endpoint is 0.15¢ per successful call, which is $1.49 per 1,000. It bills from your HProxy balance with no subscription and no monthly minimum. Errors are retried and never charged; a lookup whose target does not exist counts as a call.
The API only accesses publicly available YouTube data, the same pages anyone can open in a browser. You are responsible for using the data in line with applicable laws and YouTube's terms for your use case.
A structured JSON object with the full playlist data YouTube exposes publicly. See the fields listed above. The schema is consistent across calls, so you integrate once and rely on it.
No. Every call runs on HProxy's own residential network behind the scenes, so requests look like real users. The proxy layer is already included in the per-call price.
Docs and AI
Connect your scraper to an AI, any time.
The whole Scraper API is published as markdown, so an assistant reads every endpoint, every parameter and a real response without a key and writes your integration. And because a scrape is one GET that answers in JSON, an agent can run the scraper itself, on its own schedule, with your key.
Claude, ChatGPT, Cursor, Gemini, Copilot, Windsurf, Perplexity, Ollama and any assistant that speaks MCP.
The API as markdown
Paste /llms/scraper-api.txt into Claude, ChatGPT, Cursor or Copilot: every endpoint and the whole catalog, in one file. No key and no account to read it.
An agent can call it
One GET with your key returns structured JSON, so an agent scrapes on its own schedule. No browser to drive, no parser to keep alive between runs.
MCP server and CLI
Built by us for the free tools and hosted at mcp.hproxy.com: the proxy list, the checker and the IP lookup as tools in Claude, ChatGPT, Cursor or any assistant that speaks MCP. Nothing to install, no key.
API docs
Every scraper endpoint documented end to end, with the parameters it takes and the response it really returns.
Posts and media elsewhere
The same data on 13 other platforms.
One key, one JSON shape, one balance. Move sideways without learning a second API.
More from YouTube
13 YouTube endpoints, one key.
Every platform
The same key works on all 23.
- TikTok Scraper API23 endpoints · $1.49/1k
- Facebook Scraper API17 endpoints · $1.49/1k
- YouTube Scraper API13 endpoints · $1.49/1k
- Instagram Scraper API11 endpoints · $1.49/1k
- LinkedIn Scraper API6 endpoints · $1.49/1k
- Twitter / X Scraper API6 endpoints · $1.49/1k
- Reddit Scraper API5 endpoints · $1.49/1k
- Threads Scraper API5 endpoints · $1.49/1k
- Google Scraper API4 endpoints · $1.49/1k
- Pinterest Scraper API4 endpoints · $1.49/1k
- Twitch Scraper API4 endpoints · $1.49/1k
- Bluesky Scraper API3 endpoints · $1.49/1k
- Truth Social Scraper API3 endpoints · $1.49/1k
- Spotify Scraper API3 endpoints · $1.49/1k
- Snapchat Scraper API1 endpoint · $1.49/1k
- SoundCloud Scraper API1 endpoint · $1.49/1k
- Kick Scraper API1 endpoint · $1.49/1k
- Linktree Scraper API1 endpoint · $1.49/1k
- Komi Scraper API1 endpoint · $1.49/1k
- Pillar Scraper API1 endpoint · $1.49/1k
- Linkbio Scraper API1 endpoint · $1.49/1k
- Linkme Scraper API1 endpoint · $1.49/1k
- Amazon Scraper API1 endpoint · $1.49/1k
More on the YouTube Playlist API
What the YouTube Playlist endpoint returns
Pull a YouTube playlist in full: every video in playlist order with title, duration and channel, plus the playlist owner. The JSON object carries items[], itemCount and owner. Nothing is summarised away on our side, so what you read in the response is what the YouTube playlist page itself holds.
What you send to the YouTube Playlist API
The call takes a playlist ID. Required: playlist_id. Your key travels in the X-API-Key header, the response is JSON, and the call is billed at 0.15¢, $1.49 per 1,000.
Posts and media on other platforms
The same posts and media data is available on 13 other platforms: TikTok Video, Facebook Profile Reels, Instagram Post, LinkedIn Company Posts, Twitter / X User Tweets, Reddit Subreddit Posts, Threads User Posts, Pinterest Pin, Twitch User Videos, Bluesky User Posts, Spotify Track, Truth Social User Posts and Kick Clip. They share this endpoint's JSON shape, its per-call billing and your one API key, so moving from YouTube to another network is a change of URL rather than a second integration.
Is scraping YouTube playlist allowed?
The endpoint reads publicly available YouTube data, the same pages anyone can open in a browser without logging in. It does not touch private accounts or anything behind a password. How you then use the data is yours to keep lawful, under the rules that apply to you and to YouTube.
Ready when you are.
Your dashboard is ten seconds away. No sales call, no subscription, no minimum.