탐색으로 건너뛰기

Does the next page use a page number or continuation_token?

youtube.web_v2.get_video_comments paginates using continuation_token, not a page number. Read the continuation token from the full previous response, pass that token as continuation_token on the next request, and keep video_id, sort, language, and country unchanged.

Advancing pages with continuation_token

Follow a consistent parameter context across every page in the same comment run:

  • Read from the full response: Inspect the saved youtube.web_v2.get_video_comments response to extract the returned continuation token.
  • Pass the token unchanged: Send the returned token as continuation_token on the next call instead of passing an integer page number.
  • Keep query context fixed: Retain the exact same video_id, sort, language, and country settings on every subsequent page.

Keeping newest and top runs separate

Each sort order has its own pagination sequence:

  • When page one uses newest, request page two with newest and the continuation_token returned by page one.
  • When you want popular comments instead, start a separate top lookup from page one rather than reusing a newest continuation token.

Stop conditions and request billing

Stop paginating and record the exact stop reason whenever any of these conditions occur:

  1. continuation_token is missing from the response or repeats an earlier token.
  2. The youtube.web_v2.get_video_comments request fails.
  3. The collection reaches your configured page limit.

Each additional platform page counts as another billed request.

Comment research guide · BeatAPI pricing