Pagination

Reads are paginated with pageSize and an opaque cursor; LinkToAny absorbs every vendor-specific cursor.

Reads are paginated with a single pageSize parameter. Underneath, every platform paginates differently — cursors, page numbers — and LinkToAny absorbs those differences so you never handle a vendor-specific cursor.

cURL

curl "https://api.linktoany.com/unified/{accountId}/product?pageSize=100" \
  -H "accept: application/json" \
  -H "authorization: Bearer ak_<your_api_key>"

SDK

// Page at a time — you hold the cursor
const first = await client.records.list(accountId, 'product', { pageSize: 100 });
const next = await client.records.list(accountId, 'product', {
  pageSize: 100,
  cursor: first.pagination?.cursor ?? undefined,
});

// Or let the SDK walk every page for you
for await (const product of client.records.iterate(accountId, 'product', { pageSize: 100 })) {
  await save(product);
}

Parameter	In	Required	Description
`pageSize`	Query	No	Maximum records to return per page. The effective ceiling depends on the backing platform's own page limits — smaller of the two wins.
`cursor`	Query	No	Opaque pointer to the next page, taken from `pagination.cursor` on the previous response. Omit it to start from the first page; when the response comes back without a cursor, you have reached the end.

records.iterate(...) walks every page without you managing the cursor; records.list(...) hands the cursor back for you to hold yourself.

Writes are not paginated — each POST pushes exactly one record. For bulk pushes, send records sequentially and respect the per-system rate limits.