A single Google Calendar API list response is not necessarily the complete result. Pagination can stop an audit or synchronization after only the first page. Follow the returned continuation token before reporting a complete event or calendar inventory.
Inspect the continuation field
After each list request, check nextPageToken. Google’s pagination guide says a nonempty token means more results remain. Setting a large maxResults does not guarantee that many records arrive or eliminate the collection’s server-side page limit.
Keep the query stable
Request the next page using the same original query and set pageToken to the returned continuation value. Continue until there is no next-page token. Do not change date filters or calendar identity between pages and describe the combined result as one consistent query.
Persist enough progress for an interrupted read to be reconciled deliberately. Keep a failed page distinguishable from an empty final page instead of treating every unsuccessful request as the end of the collection.
Verify completeness within the declared scope
Record the calendar, filters, page count, and resulting identifiers. Check that the last successful response had no continuation token. Recurrence expansion is a separate choice: Google’s recurring-event guide says ordinary list results and singleEvents expansion represent parents and instances differently. A fully paginated restricted query is complete only for its declared filters and representation, not every calendar or every historical event. Use appropriate error handling and access checks throughout. The completed inventory should be supported by the actual final-page condition, rather than an assumed total inferred from a convenient round number of entries in the first response.
References
- Page through lists of resources | Google Calendar | Google for Developers
- Recurring events | Google Calendar | Google for Developers
Reviewed against the linked official product guidance on November 4, 2026. Features, limits, screen labels, and access can vary by account, platform, region, and organization policy.