YouTube · Comments

YouTube Video Comments Scraper API

The YouTube Video Comments endpoint is one API call: send a URL with your HProxy key and get back a clean, structured JSON object. Pull every comment on a YouTube video, page by page, with author, text, like count, reply count and timestamp. 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 key YouTube API reference

0.15¢ per call
$1.49 per 1,000
Takes a URL
Errors and timeouts are not charged

On YouTube

Profiles1 Posts and media5 Transcripts1Comments2Search and trends3

Comments

YouTube

TikTok

Facebook

Instagram

The call

One GET, and the video comments 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/comments?url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DdQw4w9WgXcQ" \
  -H "X-API-Key: hpx_your_key_here"

Response200 OK · JSON

{
  "count": 18432,
  "comments": [
    { "id": "72901...", "author": "@user", "text": "this is so real",
      "likeCount": 214, "replyCount": 3, "createdAt": "2026-07-14T09:12:00Z" }
  ],
  "cursor": "eyJvZmZzZXQiOjIwfQ"
}

What comes back

The YouTube video comments object.

comments[]: Each comment with author, text, like count and timestamp.
author: Commenter handle, ID and avatar.
likeCount / replyCount: Engagement on each comment.
cursor: Pagination token to pull the next page of results.

What it takes

Parameters.

urlurlRequiredhttps://www.youtube.com/watch?v=dQw4w9WgXcQ

Target URL (profile, post or video).

continuationTokenstringvalue

Pagination token from the previous response.

orderstringtop

The order parameter. Allowed values: `top`, `newest`.

How it works

Scraping YouTube video comments, in three steps.

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

Create a free account Every YouTube endpoint

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 video comments endpoint earns its keep.

Run sentiment and topic analysis on YouTube audiences.
Surface support issues or product feedback hiding in comments.
Detect spam, brigading or coordinated campaigns.

YouTube video comments questions

Answered before you ask.

The reference

Send one authenticated HTTPS request to the YouTube Video Comments endpoint with a URL and your HProxy API key. Pull every comment on a YouTube video, page by page, with author, text, like count, reply count and timestamp. 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 video comments 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 docs Set 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