Pagination & synchronization
Treat cursors as opaque and keep synchronization within one authorized scope.
Follow the selected response
Use the exact query fields, limits, response envelope, and continuation fields shown in the selected operation’s schema. Cursors are opaque: do not decode, edit, or transfer them between products, queries, credentials, locations, or revisions.
Partner Data publishes incremental synchronization shapes. Store your checkpoint only after the associated page is durably processed. A successful page does not imply that the entire dataset is complete.
Respect ordering and freshness
Use the contract’s watermarks, ordering, deletion markers, and cursor semantics. Do not substitute client wall-clock time for an authoritative checkpoint or infer deletion just because an item is absent from one page. Where a behavior is not published, coordinate with the product owner rather than assuming it.
Recover deliberately
On an invalid cursor, follow the product’s documented resynchronization behavior. Use bounded retries for rate limits and temporary dependency failures, and keep checkpoints separate for each approved location and dataset.