Pagination Parameters
| Parameter | Type | Default | Max | Description |
|---|---|---|---|---|
page | integer | 1 | - | Page number (1-indexed) |
page_size | integer | 20 | 100 | Number of items per page |
Request Example
Response Format
All paginated responses follow this structure:Response Fields
| Field | Type | Description |
|---|---|---|
count | integer | Total number of items across all pages |
next | string|null | URL for next page, or null if last page |
previous | string|null | URL for previous page, or null if first page |
results | array | Array of items for current page |
Fetching All Pages
- Python
- JavaScript
- Manual Iteration
Performance Optimization
Use Maximum Page Size
Always use the maximumpage_size (100) to minimize API calls:
Implement Cursor-Based Pagination (Future)
Cursor-based pagination is planned for future releases to improve performance on large datasets.
Filtering + Pagination
Combine filters with pagination for efficient data retrieval:Paginated Endpoints
The following endpoints support pagination:/v1/platform/businesses/- List businesses/v1/platform/businesses/{id}/invoices/- List invoices/v1/platform/businesses/{id}/invoices/payments/- List invoice payments/v1/platform/businesses/{id}/bills/- List bills/v1/platform/businesses/{id}/bills/payments/- List bill payments/v1/platform/businesses/{id}/customers/- List customers/v1/platform/businesses/{id}/vendors/- List vendors/v1/platform/businesses/{id}/general-ledger/chart-of-accounts/- List accounts/v1/platform/businesses/{id}/general-ledger/journal-entries/- List journal entries
Best Practices
Use maximum page size
Set
page_size=100 to minimize API calls and improve performance.Cache results
Cache paginated results when appropriate to reduce redundant API calls.
Monitor count field
Use the
count field to show progress when fetching all pages.Handle empty results
Always check if
results array is empty before processing.