Audience & creator discovery
Build lead and creator-discovery pipelines from YouTube public profiles. Filter by follower count, engagement, and region. The JSON is flat enough to drop into a Postgres column without normalisation.
No proxy needed. 12 pre-built endpoints, parsed JSON in seconds.
The channel scraper takes one input: handle. The response carries every public field YouTube exposes.
curl https://api.hproxy.com/v1/scrape/youtube/channel/collect/by/handle \
-H "Authorization: Bearer $HPROXY_KEY" \
-H "Content-Type: application/json" \
-d '{"handle":"ThePatMcAfeeShow"}'{
"channelId": "UCxcTeAKWJca6XyJ37_ZoKIQ",
"channel": "http://www.youtube.com/@ThePatMcAfeeShow",
"name": "The Pat McAfee Show",
"avatar": {
"image": {
"sources": [
{
"url": "https://yt3.googleusercontent.com/….jpg",
"width": 72,
"height": 72
}
]
}
},
"subscriberCount": 2750000,
"subscriberCountText": "2.75M subscribers",
"videoCountText": "9,221 videos",
"viewCountText": "2,170,355,382 views",
"joinedDateText": "Joined Aug 23, 2017",
"twitter": "https://twitter.com/PatMcAfeeShow",
"instagram": "https://instagram.com/patmcafeeshow",
"country": "United States"
}Channel metadata: subscriber count, total views, video count, join date, country, and linked social profiles.
Video metadata: title, description, view and like counts, duration, channel reference, publish date, and the thumbnail URL.
AI-fallback transcript of any video — audio-to-text when no caption exists, the published captions otherwise.
Keyword and query search results with the matched entities and the engagement metadata behind each one.
Every comment on a post or video — including reply trees, author handle, timestamp, and like count — not just the top-level reactions.
Structured trending objects returned as flat, predictable JSON — ready to drop straight into your database.
Every line is a live endpoint. Click through for the input schema, response shape, and the curl recipe.
Channel profile, subscriber count, total videos, total views, social links.
Paginated list of videos uploaded by a YouTube channel.
List of short-form videos (Shorts) from a YouTube channel.
Full YouTube video metadata, captions, related videos.
Captions / subtitles / transcript for a YouTube video.
Premium pricing — every call uses AI or heavy data extraction.
Search YouTube by keyword — videos, channels, playlists, shorts.
Top-level comments on a YouTube video.
Trending YouTube Shorts — viral short-form videos.
Search YouTube for content under a specific hashtag.
Replies to a specific YouTube comment thread.
Every video in a YouTube playlist with metadata.
Detail of a YouTube community post — text, images, like count.
Build lead and creator-discovery pipelines from YouTube public profiles. Filter by follower count, engagement, and region. The JSON is flat enough to drop into a Postgres column without normalisation.
Track every public post mentioning a brand or keyword across YouTube. Pipe captions into sentiment models and chart engagement over time without writing a single parser.
The comments endpoint carries the full reply tree, so social-listening models see the whole thread — not just top-level reactions. Real conversation data, structured.
Query YouTube by keyword or hashtag and get back the matched entities with their engagement metadata attached. Power competitive research and content-gap analysis.
The questions that come up before the first call. If yours isn’t here, the founder reads support email himself — just write in.
No. Every endpoint runs on our residential pool — fifty million IPs sourced through opt-in partner SDKs. You send an HTTP request with your API key; rotation, retries, and anti-bot handling are ours to worry about.
Each call is routed through a residential session that matches typical organic traffic patterns. We don’t advertise specifics; what matters is the result — a 99%+ success rate on public-data endpoints in real customer traffic.
Every endpoint returns a flat top-level wrapper (platform, scraper, data, creditsUsed, elapsedMs, requestId) with the parsed YouTube entity inside data. See the live example near the top of this page for the exact shape.
Public data scraping (no login, no private content, no PII beyond what youtube.com itself publishes) sits within the boundaries set by hiQ Labs v. LinkedIn and similar US/EU precedents. We don’t serve endpoints that touch authenticated content. You’re responsible for your own use of the data under your local data-protection law (GDPR, CCPA, etc.).
From $0.003 per call on the standard endpoints. Endpoints that do heavier upstream work — AI transcripts, posts with media archived to R2 — cost more. The exact per-call price shows on each endpoint row below. One call = one charge, never multiplied by record count.
Yes — the wallet starts with a $2 deposit that’s refundable for 24 hours. That’s plenty of calls to verify the response shape matches what you’re building across all 12 YouTube endpoints.
Median response time across the YouTube endpoints is under 2 seconds. Heavier endpoints (deep comment threads, cursor-paginated lists) can run 4-8 seconds depending on the page depth requested.
Sign in with Google, drop $2 in the wallet, fire your first YouTube call against youtube.com. If it doesn’t do what you need, the balance is refundable for 24 hours.