Pagination

PCX uses cursor-based pagination throughout. There is no offset-based (page=2) pagination.

How it works

Make your first request — optionally pass limit to control page size
If there are more results, the response includes a last_evaluated_key (or lastEvaluatedKey) field
Pass that value back as a query parameter on your next request to get the next page
When last_evaluated_key is null (or absent), you have reached the last page

Request

GET /v1/users/list?limit=20
GET /v1/users/list?limit=20&last_evaluated_key=<cursor_from_previous_response>

Response

{
  "status": "success",
  "data": [ ... ],
  "count": 20,
  "last_evaluated_key": "eyJwa...",
  "meta": {
    "last_evaluated_key": "eyJwa..."
  }
}

Pagination cursors are opaque tokens. Do not attempt to parse, modify, or construct them manually — they are base64-encoded and will cause a 400 if malformed.

Key naming inconsistency

Different services use slightly different field names for the pagination cursor — this is a known inconsistency:

Service	Request param	Response field
Organizations	`lastEvaluatedKey`	`lastEvaluatedKey`
Users	`last_evaluated_key`	`last_evaluated_key`
Virtual Accounts	`last_evaluated_key`	`last_evaluated_key`
Beneficiary	`last_evaluated_key`	`last_evaluated_key`
Transaction	`last_evaluated_key`	`last_evaluated_key`

​Pagination

​How it works

​Request

​Response

​Key naming inconsistency

Pagination

How it works

Request

Response

Key naming inconsistency