Nessie v2 GET /customers returns only 50 oldest-first: new customer missing from dropdown; page with ?cursor=next_cursor ({items,next_cursor}), ?after= is silently ignored
Symptoms seen while building a Next.js dashboard and a contract test suite on Nessie v2: 1. A Playwright script could not find a customer the test had just created in the dashboard's customer <select>. The dropdown was fed by a single GET /customers. 2. A test runner reported 13 'pagination mismatches' because it expected {data:[...], cursor:"..."}.
How Nessie v2 list endpoints actually page (checked with curl, Nov 2026):
- Response shape is {"items":[...], "next_cursor":"..."} (ListResponse*DTOBody in the spec). items is declared nullable, so guard with page.items ?? [].
- Default limit is 50 (max 100 on /customers, /accounts, /merchants; other endpoints differ).
- Results come oldest first. With 53 customers, the first page held the 50 oldest and the 3 newest (including the one just created) were on page 2. A freshly created entity is the LAST thing you see, not the first.
- next_cursor is the id of the last item on the page (e.g. "cust_..."). Pass it back as ?cursor=<next_cursor>.
- On the last page next_cursor is absent from the JSON (the key is omitted, not null or "").
- ?after= is the event-feed parameter (GET /events?after=<seq>). On /customers it is silently ignored: ?after=<cursor> returned page 1 again with 50 items. A loop using after never terminates.
Working loop (TypeScript):
let cursor: string | undefined; const all = [];
do {
const q = new URLSearchParams({ limit: "100", ...(cursor ? { cursor } : {}) });
const page = await fetch(${BASE}/customers?${q}, { headers }).then(r => r.json());
all.push(...(page.items ?? []));
cursor = page.next_cursor || undefined;
} while (cursor);
For a UI, either load all pages server-side in your API route, or sort/search on your side. To find something you just created, use its id (GET /customers/{id}) instead of scanning the first page.