Marble API uses offset-based pagination for endpoints that return multiple items. Pagination metadata is included in every response to help you navigate through large datasets efficiently.
import { Marble } from "@usemarble/sdk";const marble = new Marble({ apiKey: process.env["MARBLE_API_KEY"] ?? "",});const result = await marble.posts.list({ limit: 10, page: 1,});
The SDK returns an async iterable for paginated endpoints:
const result = await marble.posts.list({ limit: 10 });for await (const page of result) { console.log(page.posts); console.log(page.pagination.currentPage);}
Use the pagination response to build navigation UI:
const result = await marble.posts.list({ limit: 10, page: 1 });for await (const page of result) { const { pagination } = page; // Use these for your pagination UI const canGoBack = pagination.previousPage !== null; const canGoForward = pagination.nextPage !== null; const pageInfo = `Page ${pagination.currentPage} of ${pagination.totalPages}`; const itemCount = `${pagination.totalItems} total items`;}
The SDK’s async iterable automatically handles fetching subsequent pages. If
you only need a single page (e.g., for pagination controls), iterate once and
break.
Optimize Performance: Use smaller page sizes (5-20 items) for better
performance, especially on mobile devices.
Handle Empty Results: Always check if the data array is empty and handle
the empty state in your UI.
Navigation Logic: Use nextPage and previousPage values to build
navigation controls. These fields will be null when navigation in that
direction isn’t possible.
Building Pagination UI: The pagination object in every response gives
you everything needed for pagination controls: current page, total pages, and
next/previous page numbers.
