Pagination

List endpoints return cursor-paginated collections with a stable wrapper.

Collection endpoints return the same wrapper and use opaque cursors, so the same paging logic works across the API. The one exception is GET /v1/onramp/references, which pages with pageNumber and pageSize and returns {data, pageNumber, pageSize, count}. See Provider on-ramps.

Request parameters

limit · integer · default: "20"

Maximum items per page. Minimum 1, maximum 100.

cursor · string

An opaque cursor from a previous response’s pagination.nextCursor. Omit it on the first request.

Response shape

{
  "data": [
    { "id": "…" }
  ],
  "pagination": {
    "nextCursor": "b3BhcXVl",
    "hasMore": true
  }
}

data · array

The page of resources.

pagination.nextCursor · string | null

Pass this as cursor to fetch the next page. null when there are no more pages.

pagination.hasMore · boolean

Whether another page is available.

Paging through all results

Treat the cursor as opaque: pass it back exactly as received, and stop when hasMore is false.

cURL

# First page
curl -sS "https://api.zeam.money/gw/v1/wallets?limit=50" \
  -H "Authorization: Bearer $ZEAM_TOKEN" \
  -H "x-zeam-auth: $ZEAM_APP_SECRET"

# Next page, using nextCursor from the previous response
curl -sS "https://api.zeam.money/gw/v1/wallets?limit=50&cursor=b3BhcXVl" \
  -H "Authorization: Bearer $ZEAM_TOKEN" \
  -H "x-zeam-auth: $ZEAM_APP_SECRET"

Do not parse or construct cursors yourself. Their format is internal and may change without notice.