GET /v4/transactions

Like every V4 call, this endpoint family expects the three auth factors: a Bearer token (Authorization: Bearer …), a whitelisted source IP, and the per-request RSA signature headers (X-PP-Signature, X-PP-Nonce, X-PP-Timestamp). See Request Signing.

Newest-first list of your collections and payouts for dashboards and reconciliation. Filters are query parameters (and are covered by the request signature like everything else).

Query parameters
ParamDescription
typecollection or payout — omit for both.
statusAPI-vocabulary status, e.g. completed, pending_approval.
from / toDate bounds (inclusive), e.g. 2026-07-01.
limitPage size, 1–100 (default 25).
cursorOpaque cursor from the previous page's next_cursor.
Example
curl "https://v4api.pokeapay.com/api/v4/transactions?type=collection&status=completed&from=2026-07-01&limit=50" \
  -H "Authorization: Bearer $TOKEN" \
  -H "X-PP-Signature: $SIG" -H "X-PP-Nonce: $NONCE" -H "X-PP-Timestamp: $TS"
Response — 200
{
  "data": [
    { "type": "collection", "reference": "INV-2026-0042", "status": "completed", "amount_minor": 25000, "currency": "KES", "…": "…" }
  ],
  "next_cursor": "eyJ0cyI6IjIwMj…"
}

Pagination: pass next_cursor back as cursor to get the next page; null means you have everything. Cursors are opaque and stable — safe to resume from later. A malformed cursor → 400 {"error":"invalid_cursor"}.

Reconciliation tip: page through status=completed for the day with from/to and compare amount_minor/fee_minor totals against your statement export.