탐색으로 건너뛰기

Do I increment next_offset for the next App comment page?

No. Do not add 1 to next_offset when paging Bilibili App comments. Start bilibili.app.fetch_video_comments with next_offset:1, then inspect the full response for another page and pass the continuation value returned by that response unchanged as the next next_offset.

How next_offset continuation works

bilibili.app.fetch_video_comments uses response-driven continuation rather than sequential page counting:

  • First page: Send next_offset:1 together with the target video ID and chosen mode.
  • Subsequent pages: Read the full bilibili.app.fetch_video_comments response to confirm another page exists, then send the exact continuation value returned by the response as next_offset.
  • Unchanged request scope: Keep the video ID and mode identical across every page in the same pagination run.

Sort modes and separate pagination runs

Each mode value represents an independent comment sequence:

  • Time order (mode:2): When the first page uses mode:2, keep mode:2 and the same video ID for every subsequent page.
  • Popular comments (mode:3): To read popular comments instead, start a separate first-page request with mode:3 and next_offset:1 rather than changing mode mid-chain.
  • Web pagination flow: If you are using the Bilibili Web comments action instead of bilibili.app.fetch_video_comments, follow the separate rules in Web pagination.

Stop conditions and request counting

Stop paging and record the reason whenever any of the following occurs:

  1. The continuation value is missing from the response or repeats a value already requested.
  2. The bilibili.app.fetch_video_comments request returns an error.
  3. The collection reaches your configured page limit.

Every fetched page counts as one billed request.