Skip to main content

Pagination Parameters

Request Example

Response Format

All paginated responses follow this structure:

Response Fields

Fetching All Pages

Performance Optimization

Use Maximum Page Size

Always use the maximum page_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
See the API Reference for complete list.

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.

Next Steps

Error Handling

Handle errors during pagination

API Reference

See which endpoints support pagination