Pagination

Start with the documented filters and choose page_size and sort on the first request, where offered. When has_more is true, pass next_page_token as page_token on the next request with the same filters and API key. Omit page_size and sort from continuation requests: the token already carries them, and sending either with a token returns 400 invalid_page_token, even if its value is unchanged. Treat the token as an opaque string. Do not decode it, create page numbers or add offsets.

Fetch pages of a single list sequentially. For an exhaustive traversal of search or of a result list, send sort=id where offered and follow each next_page_token in order; other orderings can skip or repeat rows that change between requests. Reconcile after the traversal completes. To work concurrently, partition competition work across independent editions or classes. Every page costs the operation's price whatever its size, and the default page size is the largest, so it needs the fewest pages and credits.