How many to return, up to 50. More than that — or less than one — is refused
with
400 rather than quietly trimmed.The cursor from the previous page’s
links.next. Do not build it yourself, and
do not hold on to it. page[before] walks the other way.links.next until it is absent. That is the whole protocol:
Why a cursor and not a page number
A partner walking a whole inventory takes minutes, and an inventory is live: a listing added halfway through shifts every row after it. An offset paginator then skips rows or repeats them, silently. A cursor does not. Listings, orders, conversations, messages and notifications page by cursor. The shorter lists that do not move under you page by number instead —/v1/sellers,
the watch models, a business’s invoices, quick replies and blocked buyers, and in
the app the address book, favorites, saved searches, devices, blocks and the
content pages. Those take page[number] (from 1) and page[size] (up to
50, 25 by default; more, or less than one, is 400 as well), and answer with first, last, prev and next links;
following links.next still works the same way. A collection refuses the other
kind’s parameters with 400.
A listing collection takes either: page[limit] and page[after] to walk it,
page[number] and page[size] for numbered pages, which is what a ranked search
in the app uses.
Without any page[...] a collection answers its first page — 25 rows, or for quick
replies 50, which is a shop’s maximum, so one page holds them all — with links.next
when there is more. Sending nothing is not a way to get everything.
Lists that are not paged
A few lists always come back whole, with nolinks.next, and are not to be sent page[...],
because each is short by nature or capped where it is made: