Video › Comment › Replies

Where to start. The id of a top-level comment: a top-level comment id (e.g. the comment.id of any row from /v1/youtube/video/comments). For the next page of replies, send pagination.next_cursor as cursor with the same continuationToken.

Text format for reply bodies: 'html' (default) or 'plainText'.

Set to 1 to get the price of this call without making it: data.dry_run carries credits_min and credits_max. Nothing is charged.

Only rows published on or after this date: YYYY-MM-DD (midnight UTC) or an ISO 8601 timestamp. Rows older than it are left off each page. This list is not in date order, so the walk does not stop at the date: keep following next_cursor, and each page costs what a page costs even when every row on it is filtered out. A row with no date is kept.

Only rows published on or before this date: YYYY-MM-DD (that whole UTC day is included) or an ISO 8601 timestamp. Newer rows are left off each page and the walk does not stop, so older pages follow. A row with no date is kept.

Universal pagination cursor. Send pagination.next_cursor from the previous response back verbatim: the API maps it to this endpoint's native continuationToken (cursor style). You never construct, decode, or look up a cursor. Omit it for page 1.