Skip to main content
Many of the API endpoints support cursor-based pagination. When a page is requested, the response includes cursors for the next and previous page of results.
All of our SDKs have built-in pagination support. Please see the individual GitHub documentation for your preferred SDK for more details.

Using cursors

If present, the next_cursor and previous_cursor values can be used to request the next and previous page of results by passing the cursor query parameter with the value of either cursor.
When you filter list transactions on broad values such as amount_eq, currency, country, or method, combine the filter with a created_at_gte and created_at_lte range for the best performance.

Page limits

Any of the APIs that support cursor pagination also support the limit query parameter to control the number of items returned. Check the reference documentation for each endpoint for the range of limit values allowed.