Skip to main content
List endpoints return results in pages. You control the page size with limit and move through pages with cursor.

How it works

  1. Send the first request without a cursor.
  2. Read data.context.hasMore in the response.
  3. If it’s true, send the same request again with cursor set to data.context.nextCursor.
  4. Stop when hasMore is false.
Treat the cursor as an opaque value and pass it back unchanged. Drive the loop with hasMore, not by comparing the number of results to limit. A short page doesn’t prove you’ve reached the end.

Page size

Most list endpoints accept a limit of 1 to 100. The default varies by endpoint, so check the endpoint page. Keep every other filter identical across pages, otherwise the cursor won’t line up.

Example

Endpoints that use it

Vendor List, Invoice List, Purchase Order List, Expense List, Reimbursement List, Payment Request List and User List. Some small lists return everything in one response, such as the TDS and GST tax lists.
The context fields differ slightly between endpoints. For example, count means the total matches on some and the size of the current page on others, and nextCursor is a number on User List. Check the response table on the endpoint page when you rely on those details.