YouTube Shorts Scraper - Views, Likes & Channel Data

details-fetched

Charged once per Short when 'Exact view counts, duration, publish date and description' is on, and charged strictly per set of statistics obtained rather than per request attempted. A channel's Shorts tab only ever states a rounded view count - "12M views" is anything from 12,000,000 to 12,999,999 - and this replaces it with the exact figure (measured: 12,576,545 where the list said 12M), then adds the duration in whole seconds, the publish time as a true UTC timestamp, and the full description. Every row records which kind of view count it got in viewCountIsExact, so rounded and exact figures are never mixed up in a spreadsheet. YouTube applies a bot check to one of the two requests behind this option, based on the IP address a run happens to be given. The exact view count is read from whichever source answers and is unaffected; duration, publish date and description come only from the checked request and are left empty when it is refused - measured on a full run, exact views arrived on 100% of rows and the other three on about half. Those Shorts are counted in each summary row as detailsGated, so an empty cell always has a number explaining it. A Short for which NO statistics could be obtained is not charged at all, and neither is a Short dropped by the minimum-views filter after its exact count came back - with this option on, the filter is applied to the exact number rather than the rounded one.

likes-fetched

Charged once per exact like count obtained, when 'Also fetch exact like counts' is on. It is priced above the exact-statistics event because it costs far more to produce: YouTube publishes no like count anywhere on a Shorts listing, and the only response that carries the real number is about fifteen times the size of the one carrying exact views. It is charged per COUNT, not per request. A Short whose like count YouTube withholds, or whose request failed, is written with likeCount null and is not charged for it - so you are never billed for an empty column. The summary row's likesFetched is the exact number of charges raised for the channel, which makes the bill checkable against the dataset. Worth knowing if you are also using exact statistics: the same response carries the exact view count, so switching like counts on makes exact views more reliable at no extra request and no extra charge.