> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.beatapi.io/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.beatapi.io/_mcp/server.

# Do I increment cursor for the next page?

> Do not add 1 to cursor on douyin.app.v3.fetch_video_comments; pass the exact cursor returned by the previous response unchanged while keeping the same aweme_id.

No. Never increment `cursor` manually by `1`. For every subsequent page on `douyin.app.v3.fetch_video_comments`, pass the exact cursor value returned by the previous response unchanged while keeping the same video `aweme_id`.

## Chain pages cleanly

1. Start the first call to `POST /v1/social-data/call` with `aweme_id` as a string and `cursor: 0`.
2. Read the returned cursor directly from the live response payload, pass the returned value unchanged as `cursor` on the next call for the same `aweme_id`, and save each page as a separate file.
3. For example, when page 1 reveals installation questions and a broader sample across other product models is needed, request page 2 with page 1's returned cursor rather than guessing the next integer.

## Stop conditions and failure handling

Stop paginating immediately when any of four conditions occurs:

* The planned page cap is reached.
* The response omits a cursor or repeats an earlier cursor.
* The returned batch contains zero comments.
* A page request fails.

Record the exact number of pages fetched in the final notes. When a later page fails, failed calls do not consume credits; store the failed page's parameters and `request_id` for follow-up while continuing review on the pages already saved.

## Contracts and related questions

Before running the request, inspect the `data:douyin.app.v3.fetch_video_comments` contract for free.

[Back to Douyin questions](/faq/douyin).