Skip to main content
GET
Get Wallet Transaction History

Overview

Retrieve paginated transaction history for any wallet type. Returns up to 10 transactions per page, ordered by date descending (newest first). Supports credit, reward, and internal wallet types with filtering and pagination. Use Cases:
  • Display transaction history to users
  • Generate transaction reports or statements
  • Audit wallet activity
  • Track deposits, withdrawals, and purchases
  • Reconcile balances

Authentication

string
required
Your public API client key
string
required
Bearer token for authentication

Query Parameters

string
required
Wallet identifier obtained from wallet details endpoint (e.g., from GET /v1/wallet/credit, /v1/wallet/reward, or /v1/wallet/internal)
string
required
Type of wallet to query: CREDIT, REWARD, or INTERNAL
string
Wallet currency (required only if walletType is INTERNAL). Examples: “usdc”, “usdt”, “xrp”
string
Page number for pagination, zero-indexed. Defaults to page 0 if omitted or invalid. Each page returns up to 10 transactions.
boolean
default:false
Route to US backend environment

Response

Returns an array of transaction objects, up to 10 per page.
string
Transaction description (e.g., “Credit withdrawal”, “Card purchase”, “Deposit”)
string
Transaction amount (decimal string)
string
Currency code (e.g., “usdc”, “usdt”, “xrp”)
string
Transaction direction: "debit" for outgoing, "credit" for incoming
string
ISO 8601 timestamp of the transaction

Code Examples

Pagination Example

Complete Pagination Implementation

Integration Patterns

Transaction Display with Formatting

Filter Transactions by Type

Calculate Period Summary

Important Notes

Page Size: Each page returns up to 10 transactions. If a page has fewer than 10 transactions, you’ve reached the end of the history.
Zero-Indexed Pagination: Page numbers start at 0. First page is page=0, second page is page=1, etc.
Internal Wallet Currency: When querying history for INTERNAL wallet type, you must provide the walletCurrency parameter. Omitting it will result in an error.

Edge Cases

Empty History

A wallet with no transactions returns an empty array:

Invalid Page Numbers

Invalid or out-of-range page numbers default to page 0:

Transaction Ordering

Transactions are always ordered by date descending (newest first). To get oldest first, reverse the array:

Large History Sets

For wallets with thousands of transactions:
  • Implement efficient pagination with loading indicators
  • Cache historical data client-side
  • Consider date range filters for performance
  • Lazy-load transactions as user scrolls