YouTube Comments & Replies Scraper API — $0.50/1K avatar

YouTube Comments & Replies Scraper API — $0.50/1K

Pricing

from $0.50 / 1,000 results

Go to Apify Store
YouTube Comments & Replies Scraper API — $0.50/1K

YouTube Comments & Replies Scraper API — $0.50/1K

Export public YouTube comments and reply threads to structured JSON, CSV, or Excel with author channels, likes, timestamps, pinned flags, and creator hearts. No YouTube API key, browser, proxy, or login. $0.50 per 1,000 results.

Pricing

from $0.50 / 1,000 results

Rating

0.0

(0)

Developer

Coor Yu

Coor Yu

Maintained by Community

Actor stats

0

Bookmarked

1

Total users

0

Monthly active users

20 hours ago

Last modified

Categories

Share

Export public YouTube comments and reply threads as structured dataset rows. The Actor uses YouTube's public web responses directly, so normal runs need no Google API key, browser, login, proxy, or residential IP.

What you get

  • One dataset row per top-level comment or reply.
  • Comment text, author/channel identity, avatar, likes, reply count, pinned and creator-heart flags.
  • Top-comments or newest-first ordering.
  • Exact per-video and per-thread limits with ID-based de-duplication.
  • HTTP-only execution with bounded concurrency, timeouts, and retries.

Pricing

  • Result fee: $0.0005 per dataset row — $0.50 per 1,000 comments or replies.
  • A small Actor start event and normal Apify platform usage may also apply; see the Pricing tab.
  • Rows that are not written to the dataset are not charged as results.

Example input

{
"videoUrls": ["https://www.youtube.com/watch?v=dQw4w9WgXcQ"],
"commentsPerVideo": 100,
"includeReplies": true,
"repliesPerComment": 20,
"sortBy": "top",
"maxConcurrency": 6
}

commentsPerVideo=0 and repliesPerComment=0 mean all available rows. Deleted, held-for-review, members-only, private, age-restricted, disabled, or otherwise unavailable comments cannot be returned.

Reliability and cost controls

  • No browser image or proxy transfer is used.
  • Global HTTP concurrency is bounded across videos and replies.
  • Opaque YouTube continuation tokens are followed sequentially so pages are not skipped.
  • HTTP 429/5xx responses receive short exponential retries.
  • A complete run that produces zero valid rows fails instead of reporting a misleading success.

Scrape only public data and comply with applicable laws and platform terms. Avoid collecting or processing personal data without a lawful purpose.