Skip to main content
Retrieve the full transaction history for a wallet, paginated and sorted newest-first. Every authorisation attempt is recorded — including those that were blocked by spend controls or the merchant allowlist. The decision field tells you the outcome, and blockReason explains why a transaction was rejected, making it straightforward to surface this information in a dashboard or agent audit log.

Endpoint

Authentication

Requires a valid Session JWT in the Authorization header.

Path Parameters

string
required
The UUID of the wallet whose transaction history you want to retrieve.

Query Parameters

integer
default:"1"
The page number to retrieve. Pages are 1-indexed.
integer
default:"10"
The number of records to return per page.

Response 200 OK

The response envelope contains success: true, a data array of transaction records, and a pagination object with totals.
boolean
Always true for a successful response.
object[]
Array of transaction records for the requested page, sorted newest-first.
object
Metadata about the paginated result set.

Example Response

Understanding decision and blockReason


Error Responses