A list can look correct on its first page while skipping or repeating records on the next. This happens when new items arrive, sort values change or a connection forgets the original filter. Agree how browsing differs from a complete export before accepting the API.
Related service: Custom software development- 01Choose the filter and ordering rules.
- 02Return a bounded page of authorized records.
- 03Provide a continuation value.
- 04Keep the request meaning consistent.
- 05Finish or restart according to documented rules.
SECTION 01
Ask what can change between pages
Pagination divides a large list into smaller responses. Offset pagination skips a number of rows; cursor-style pagination continues from a position. Neither label alone tells a buyer what happens when records change. Specify a deterministic order, such as creation time plus a unique identifier, and decide how edited sort values affect browsing.
Google's API guidance recommends consistent request arguments when continuing a paginated request and an explicit end condition. Database isolation controls which changes a query can observe, but separate requests need an intentional consistency design. Ask the agency to explain the observable behavior rather than simply say that the endpoint supports page numbers.
SECTION 02
Illustrative example: reviewing newly submitted requests
Suppose a manager browses requests ordered newest first. Between the first and second page, five new requests arrive. A naive row offset can show items from the first page again. A continuation anchored to the agreed position can avoid that particular shift, although later edits may still require defined handling.
Now the manager asks for a complete list as it stood at opening time. That is a different requirement. The system might create an export job against an agreed snapshot or fixed selection rather than reuse the live browser list. This hypothetical example separates convenient browsing from a record set that must be reconciled later.
SECTION 03
Compare behavior with realistic concurrent changes
A small internal screen may need only documented live browsing with a refresh action. Do not purchase snapshot infrastructure merely because the word pagination sounds technical. For recurring reconciliation or account exports, however, completeness may matter enough to justify a separately generated result with a timestamp and filter summary.
Ask for tests that insert, delete and edit records between page requests. Use equal sort timestamps to test the tie-breaker, change a filter while retaining an old token, and try a token under another account. Confirm token expiry, maximum page size and the exact end signal. Permission checks must run for each request; an opaque continuation value is not authorization to read the records it describes.
SECTION 04
Frequently asked questions
Are cursor-based lists always consistent?
No. A cursor can stabilize navigation without freezing the underlying data. Snapshot and change behavior still need to be specified and tested.
Can we change filters midway through a list?
Normally start a fresh traversal when the request meaning changes. Reusing an old continuation with different filters should be rejected or handled under a documented contract.
Should an export reuse the same list endpoint?
Only if its consistency and completeness satisfy the export requirement. A dedicated export job may be clearer when a reproducible, timestamped selection is needed.
PRIMARY REFERENCES
Sources and further reading
These references cover the standards, platforms, or published prices discussed in the guide. Worked examples and checklists are our editorial guidance.
- Pagination design guidanceGoogle
- Transaction isolationPostgreSQL
EDITORIAL METHOD
About this guide
We use AI to assist with drafting and editing. Catapult AI Work is responsible for the published content. Examples illustrate possible approaches; they are not client case studies unless identified as such.
Budget examples are not Catapult package prices. Check linked provider pages for current fees and plan limits before making a purchase.
Read the editorial policy