Skip to main content
Reviewed public list endpoints in the Zentra API return paginated results to keep response times predictable and payloads bounded, but the query style can vary by resource.

How It Works

Transfers and virtual accounts currently document page plus limit:
Cards currently document limit plus offset:

Parameters

Response Format

Paginated responses include a pagination object with metadata:

Pagination Object

Examples

Fetching First Transfer Page

Fetching All Transfer Pages

Filtering with Pagination

Combine pagination with filters for more specific queries:

Sorting

Sorting support varies by resource. For example, reviewed virtual account listing supports:

Performance Tips

When fetching multiple pages, use limit=100 to minimize the number of requests.
Apply filters to reduce the dataset before paginating.
Cache paginated results when possible to avoid repeated API calls.
Instead of polling for new data, use webhooks for real-time updates.
Fetching very high page numbers can be slow. Prefer date-range filters or incremental sync patterns where supported.

Cursor-Based Pagination

Cursor-based pagination is not currently part of the reviewed public gateway contract. If Zentra introduces it later, it will be documented as a separate reviewed route shape instead of being implied by the current page-and-limit contract.

Reviewed List Endpoints

The following reviewed public endpoints currently document paginated list behavior:

Common Patterns

Infinite Scroll

Pagination Controls