Skip to main content
GET
List Transactions
Retrieve a paginated list of your transactions, newest first, with optional filtering by status and date range.

Example Request

Query Parameters

This endpoint filters on status and date only. To also filter by currency, type or reference, use List Wallet Transactions, which reads the same transactions.
Transactions with status failed are left out unless you ask for them with status=failed.

Example Response

Amounts are in minor units — 500000 is ₦5,000.00. Fields that do not apply to a transaction are omitted rather than returned as null.

Payment tracking references

A cross-border payout carries uetr and tracking_codes once the SWIFT network returns them — the references a beneficiary’s bank is chased with.
Both fields are omitted until the reference exists — they are not returned as null. The UETR is assigned by the correspondent network after the payout is sent, typically within minutes but sometimes hours later, so a payout read back immediately after you create it will not carry one. Local-rail and stablecoin payouts never get one. Branch on the field’s presence; never block your flow waiting for it.
To be told the moment a UETR lands rather than polling for it, subscribe to the transaction.uetr.assigned webhook. It carries the same value.

Identifying the transfer method on deposits

Incoming deposits carry a payment_rail field saying how the money arrived, so you can reconcile per channel rather than parsing the description. There is no swift value; an international wire is the SWIFT case. The field is omitted (not null) when the provider does not report a transfer method, and never appears on payouts or crypto deposits — treat its absence as “rail unknown”. The same field is delivered on the deposit webhook.
Use date range filters to export transaction data for specific periods. Combine with status filter to find failed transactions that may need to be retried.

Authorizations

X-API-Key
string
header
required

Your Rolla API key

Query Parameters

page
integer
default:1

Page number, starting at 1.

Required range: x >= 1
pageSize
integer
default:20

Rows per page.

Required range: x >= 1
status
enum<string>

Filter by status. completed also returns pending transactions operations have already claimed, which are reported as completed.

Available options:
draft,
pending,
processing,
completed,
sent,
failed,
rejected,
refunded,
negotiating,
cancelled,
exception
Example:

"completed"

startDate
string

Inclusive start, YYYY-MM-DD or a full ISO-8601 timestamp.

Example:

"2024-01-01"

endDate
string

Inclusive end, YYYY-MM-DD or a full ISO-8601 timestamp.

Example:

"2024-01-31"

Response

A page of transactions

status
integer
required
Example:

200

message
string
required
Example:

"Transactions retrieved successfully"

success
boolean
required
Example:

true

data
object
required

A page of transactions, newest first, with its paging fields alongside.