Pagination
Cursor-based pagination for list endpoints.
EzPays uses cursor-based pagination. Every list endpoint returns:
{
"data": [ /* up to `limit` items */ ],
"page": {
"has_more": true,
"next_cursor": "eyJ0aW1lIjoxNzQ..."
}
}To fetch the next page, send the next_cursor value as the cursor query parameter:
curl 'https://api.ezpays.app/api/public/v1/payment-links?limit=50&cursor=eyJ0aW1lI...' \
-H "Authorization: Bearer ezp_live_..."When has_more is false, you've reached the end and next_cursor is null.
Parameters
| Param | Type | Default | Max |
|---|---|---|---|
limit | integer | 25 | 100 |
cursor | string | none | — |
Notes
- Cursors are opaque. Don't try to parse them — the format may change.
- Pages are stable: items added after you start a paginated walk will not retroactively appear in earlier pages.
- Items deleted between page fetches are silently skipped.
- A cursor never expires, but using a stale cursor against a different filter set may return surprising results — always pair
cursorwith the same query parameters used to obtain it.