vulns.co
/
GKData.io MCP and API Buy me a coffee

Google

Google AIP-158: pagination continuation does not grant resource authority

A page token says where to continue a result set; it does not grant permission to read it. Google's approved pagination guidance requires opaque tokens and authorization on every request. Later requests keep the other query arguments while allowing page size to change; hiding the token's format protects the interface design rather than conferring access rights.

Open the referenceImplementation GuideReviewed 2026-10-04

How to use this reference

Editorial lesson: document where pagination continues separately from who may read the results. An integration reusing a saved page token must still rely on the service to authorize every request. Keeping query arguments consistent preserves the pagination contract; it does not prove permission to access the data.

Before reading

  • Basic familiarity with paginated collection APIs and access-control modeling

Context and limits

  • The page's Created and Updated fields both display 2019-02-18, although its changelog includes 2025-07-08. The linked first-party commit corroborates that later edit; the header is not treated as the current text's last revision date.
  • Query-argument consistency excludes page size: the guidance requires honoring a changed page size and recommends rejecting changes to other arguments. This contract does not establish snapshot isolation or a fixed collection across pages.
  • Opaque token format does not establish permission. This guide supplies no incident, affected-product, bounty, or deployment-specific security claim.

Sources

  1. AIP-158: PaginationGoogle · reviewed 2026-10-04
  2. fix(AIP-158): clarify degraded skip response guidance (#1510)Google AIP maintainers · reviewed 2026-10-04

Record reviewed 2026-10-04. Snapshot af2809c308fc. Open the complete JSON contract.

Library synced 2026-11-18 · cases last reviewed 2026-10-05

af2809c308fc · JSON exports & schemas · CC BY 4.0 content / MIT software