Monitor YouTube comments for leads: what the API allows

Someone's "honest review" of your competitor sits at 400 comments. The pinned one is the creator's. The one with 37 likes, posted three days ago, says: "Dropped this after two months, the reporting is a mess. What are you all using instead?

Someone's "honest review" of your competitor sits at 400 comments. The pinned one is the creator's. The one with 37 likes, posted three days ago, says: "Dropped this after two months, the reporting is a mess. What are you all using instead?" Eleven people answered with a tool name. None of them was yours, because nobody on your team reads the comments under a video about someone else's product. Reddit and Hacker News get your attention because they feel like where buyers talk. YouTube comments are the same conversation with a worse search box. This post covers what the YouTube Data API lets you poll, what it lets you keep, and what gets your channel flagged. We read every limit below on the live Google pages on 13 October 2026.

The comment endpoint costs one unit and search got its own bucket

Google's quota table lists commentThreads.list at 1 unit per call. The table also changed this year. An archived copy from 3 January 2026 gives a default of 10,000 units a day with search.list at 100 units per call. The live page, last updated 8 October 2026, says projects get "100 search.list calls, 100 videos.insert calls, and 10,000 units per day combined for all other endpoints." Search now lists "100 quota per day. Each call costs 1 quota."

That is a real difference for a monitor. Under the old table, 100 searches would eat the whole day's budget. Now you can spend 100 searches finding videos and still have 10,000 units left to read comments. We do not know when the change landed, only that the two snapshots disagree. Check the page before you size anything, because Google can move it again.

One trap: the page says every request "even if invalid" costs at least one unit, and each extra page of results costs the unit again. A loop with a bug burns quota the same as a loop that works.

One channel ID covers every video a competitor has

You do not need to search for videos at all. The commentThreads.list reference takes either videoId or allThreadsRelatedToChannelId, which returns threads across the whole channel. maxResults runs from 1 to 100 (default 20), order accepts time or relevance, and searchTerms filters to comments containing your words. A channels.list call with forHandle turns an @handle into the channel ID.

That makes the poll small. Take 30 competitor and category channels, request the 100 newest threads each, once an hour:

1. 30 channels times 24 polls is 720 calls a day.
2. At 1 unit each, that is 720 of your 10,000 units.
3. A video with comments turned off returns a 403 commentsDisabled error. Catch it and move on.

This is our arithmetic on Google's numbers, not a Google figure. It assumes a channel gets fewer than 100 new threads an hour, so check a busy channel and poll it more often if it does not.

Scoring comes after the pull

A raw pull of competitor comments is mostly noise: "great video", timestamps, spam from other people's bots. The signal is a small fraction, and sorting it is the same job as on any other platform. Our anatomy of a high-intent Reddit post lists the cues, and LLM intent classification covers scoring them in bulk. In YouTube comments, three patterns carry most of it, and this part is our opinion from reading them, not a measured rate:

• "What do you use instead of X?" under a review of X.
• "Does this work with Y?" under a tutorial for a tool in your category.
• "Cancelling X, any alternatives?" with a reply thread of strangers answering.

Our opinion is that tutorials matter more than reviews. A two-year-old "how to set up X" video keeps ranking in search, so it keeps collecting fresh questions long after the creator stopped caring.

You can keep a comment for 30 days

The YouTube API Developer Policies limit storage. Non-authorized API data may be stored "for as long as is necessary for the purposes of the API Client but not longer than 30 calendar days," and after that the client "must either delete or refresh the stored data." The page was last updated 14 September 2026.

If you outgrow the quota, the same policies say you can apply for an extension by completing an API Compliance Audit "where you must specify the use case." That is a form and a review, so treat it as a plan for later.

Scraping the page and automating the reply are both out

The Developer Policies are blunt on scraping: clients "must not, and must not encourage, enable, or require others to, directly or indirectly, scrape YouTube Applications or Google Applications, or obtain scraped YouTube data or content." The Terms of Service separately bar accessing the Service "using any automated means (such as robots, botnets or scrapers)" without YouTube's written permission, and list collecting information that might identify a person, "for example, usernames or faces," among the prohibited acts. In our reading, the API is the sanctioned route and a headless browser on the watch page is not. We are not lawyers.

Replies get a second rule. The policies prohibit clients from automating "views, uploads, comments, likes, dislikes, or other actions without the user's prior specific and express consent." An auto-reply bot that posts "have you tried our tool?" under every match fails that test and the next one. Read in the API, reply by hand.

A canned reply under many videos costs you the channel

YouTube's spam policy defines comment spam as "high-volume, repetitive, or deceptive comments, live chats, or other messages to drive traffic to or engagement with content," and its example is posting "identical or similar 'check out my channel' messages across hundreds of videos." Violations can bring a warning or a strike, and "if you get 3 strikes within 90 days, your channel may be terminated."

Your company channel is the thing at risk, and it is also your proof you exist when someone clicks your name. The reply that survives is the one a human writes after reading the whole comment, answers the question first, and says whose product they are talking about. It is the same discipline as replying on Reddit without getting banned, with a three-strike rule attached.

Build it yourself or buy the add-on

Shadow Inbox is our product and it does not watch YouTube. It reads Reddit and Hacker News. If YouTube is where your buyers ask, the options are the ones in the GitHub monitoring post: write a small poller against the free quota, or pay for someone else's. Syften lists YouTube as a +$20 a month add-on on its Standard and PRO plans, per its pricing page on 13 October 2026. In our estimate a poller is a weekend of developer time, plus the filters you would write anyway.

Unlike X, where the free tier is gone, YouTube still gives you 10,000 units a day for nothing. The catch is not price. The catch is that your reply has to come from a person who watched the video.

● FAQ

Can you monitor YouTube comments for leads with the official API?

Yes. The commentThreads.list method returns up to 100 top-level threads per call, takes a videoId or a channel ID, and costs 1 quota unit. The default project quota is 10,000 units a day for everything except search and video uploads, so watching a few dozen competitor channels hourly uses a small slice of it.

How much does the YouTube Data API cost to read comments?

Nothing in money. The cost is quota, and Google's quota table lists commentThreads.list at 1 unit per call against 10,000 free units a day. Pagination counts: every extra page of results costs the same unit again.

Can I store YouTube comments in my CRM?

Not for long, going by the Developer Policies. Non-authorized API data may be stored temporarily for no longer than 30 calendar days, and after that you delete it or refresh it from the API. Keep the comment ID and re-fetch instead of building a permanent archive.

Is it okay to reply to the same question under many videos?

No. YouTube's spam policy lists high-volume, repetitive comments that drive traffic as comment spam, and gives identical messages across hundreds of videos as its example. Three strikes within 90 days can terminate the channel you post from.