Reference

Pagination & filtering

List endpoints use simple limit/offset pagination. There are no cursors and no Link headers.

Parameters

limit — rows per page. Defaults vary per endpoint (commonly 20–50) and are capped server-side.
offset — rows to skip. Combine with a stable sort to iterate.
Results are ordered newest-first by creation time unless the endpoint states otherwise.

cURL

curl -X POST https://centuryvtu.com/_serverFn/listTransactions \
  -H "Authorization: Bearer $CENTURY_ACCESS_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"data":{"limit":50,"offset":0}}'

Iterating safely

Offsets shift

New rows arriving mid-iteration push older rows down a page, so a naive offset walk can repeat or skip records. Anchor on a timestamp or transaction reference and de-duplicate on your side.

JavaScript

const seen = new Set();
let offset = 0;

for (;;) {
  const page = await listTransactions({ limit: 50, offset });
  if (page.length === 0) break;
  for (const tx of page) if (!seen.has(tx.reference)) { seen.add(tx.reference); handle(tx); }
  offset += 50;
}

Filtering

Filters are endpoint-specific — status, service type and date range where supported. Anything not documented on the endpoint is not supported; filter client-side after fetching rather than guessing at query parameters.