How it works
Every list endpoint accepts two optional query parameters:
Each response includes:
The
lastEvaluatedKey token is opaque — do not parse or construct it manually. Always use the value returned directly from the previous response.Endpoints that support pagination
Cursor-based pagination is available on the following endpoints:GET /v1/paymentsGET /v1/subscriptionsGET /v1/contactsGET /v1/formsGET /v1/analytics/webhook-logsGET /v1/analytics/api-metrics
Step-by-step walkthrough
1
Make your first request
Call the list endpoint without a The response will look like this:
lastEvaluatedKey. You can optionally set limit to control how many records are returned per page (up to 100).2
Check hasMore
If
hasMore is true, more records exist beyond this page. If hasMore is false, you have received all available records and you can stop.3
Pass lastEvaluatedKey for the next page
Include the Repeat this process until
lastEvaluatedKey value from the previous response as a query parameter in your next request.hasMore is false.