YouTube · Comments

YouTube Comment Replies Scraper API

The YouTube Comment Replies endpoint is one API call: send a continuationToken with your HProxy key and get back a clean, structured JSON object. Pull the full reply thread under any YouTube comment, with authors, like counts and timestamps at every level. HProxy runs the proxies, sessions, anti-bot handling and parsing server-side, so there is no headless browser to babysit and no parser to keep fixing when YouTube changes its markup. You only ever touch the JSON. Longer result sets come back page by page with a cursor, so you can walk the whole set without holding it in memory.
Get your API keyYouTube API reference
  • 0.15¢ per call
  • $1.49 per 1,000
  • Takes a continuationToken
  • Errors and timeouts are not charged

On YouTube

Profiles1Posts and media5Transcripts1Comments2Search and trends3

Comments

YouTubeTikTokFacebookInstagramReddit

The call

One GET, and the comment replies comes back as JSON.

Your key goes in one header. 1 required parameter, and the answer is the object below it.

The full reference
curl "https://hproxy.com/api/v1/scrape/youtube/comment-replies?continuationToken=value" \
  -H "X-API-Key: hpx_your_key_here"
Response200 OK · JSON
{
  "parentId": "72901...",
  "replies": [
    { "id": "72944...", "author": "@user", "text": "same thing happened to me",
      "depth": 1, "likeCount": 12, "createdAt": "2026-07-14T09:31:00Z" }
  ],
  "cursor": "eyJvZmZzZXQiOjIwfQ"
}

What comes back

The YouTube comment replies object.

replies[]
Each reply with author, text, likes and timestamp.
parentId
The comment this thread hangs off.
depth
Nesting level, so you can rebuild the thread tree.
cursor
Pagination token to pull the next page of results.

What it takes

Parameters.

continuationTokenstringRequiredvalue

Pagination token from the previous response.

How it works

Scraping YouTube comment replies, in three steps.

You write one line. Proxies, anti-bot walls, rendering and parsing happen on our side.

Create a free accountEvery YouTube endpoint
  1. 1

    Create a free account

    Sign up and top up any amount. The balance pays for every HProxy product.
  2. 2

    Grab your API key

    One key from the dashboard authenticates every scraper.
  3. 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 comment replies endpoint earns its keep.

  • Rebuild whole YouTube conversations, not just top-level reactions.
  • Find the replies where a brand actually gets answered.
  • Measure how deep a thread goes before it dies.

YouTube comment replies questions

Answered before you ask.

The reference

Send one authenticated HTTPS request to the YouTube Comment Replies endpoint with a continuationToken and your HProxy API key. Pull the full reply thread under any YouTube comment, with authors, like counts and timestamps at every level. 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.

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.

A structured JSON object with the full comment replies data YouTube exposes publicly. See the fields listed above. The schema is consistent across calls, so you integrate once and rely on it.

Yes. The response carries a cursor; pass it back on the next call to continue from where you stopped. Each page is one billable call, so you only pay for the depth you actually pull.

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.

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.

Read the scraper docsSet up your assistant

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.

Open the markdown

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.

See the endpoints

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.

Add it to your assistant

API docs

Every scraper endpoint documented end to end, with the parameters it takes and the response it really returns.

Read the docs

Comments elsewhere

The same data on 4 other platforms.

One key, one JSON shape, one balance. Move sideways without learning a second API.

Comment Scraper API
TikTok Comment Replies23 endpoints on TikTokFacebook Comment Replies17 endpoints on FacebookInstagram Post Comments11 endpoints on InstagramReddit Post Comments5 endpoints on Reddit

More from YouTube

13 YouTube endpoints, one key.

The YouTube catalog
YouTube Video CommentsCommentsYouTube ChannelProfilesYouTube Channel VideosPosts and mediaYouTube Channel ShortsPosts and mediaYouTube VideoPosts and mediaYouTube Video TranscriptTranscriptsYouTube SearchSearch and trendsYouTube Trending ShortsSearch and trendsYouTube Hashtag SearchSearch and trends

Every platform

The same key works on all 23.

The whole catalog

More on the YouTube Comment Replies API

What the YouTube Comment Replies endpoint returns

Pull the full reply thread under any YouTube comment, with authors, like counts and timestamps at every level. The JSON object carries replies[], parentId, depth and cursor. Nothing is summarised away on our side, so what you read in the response is what the YouTube comment replies page itself holds.

What you send to the YouTube Comment Replies API

The call takes a continuationToken. Required: continuationToken. 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.

Comments on other platforms

The same comments data is available on 4 other platforms: TikTok Comment Replies, Facebook Comment Replies, Instagram Post Comments and Reddit Post Comments. 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 comment replies 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.

Get startedSee every scraperTalk to us