Skip to main content
Retrieve transaction history with flexible filtering options. Transactions are returned in descending order (most recent first) with a default limit of 20 per page.
cURL

Filtering transactions

Use query parameters to filter and narrow down transaction results.

Filter by customer

Get all transactions for a specific customer:
Or use your platform’s customer ID:

Filter by transaction type

Get only incoming or outgoing transactions:

Filter by status

Get transactions in a specific status:
Available statuses:
  • PENDING - Transaction initiated, awaiting processing
  • PROCESSING - Transaction in progress
  • COMPLETED - Transaction successfully completed
  • FAILED - Transaction failed
  • EXPIRED - Quote expired before execution

Filter by date range

Get transactions within a specific date range:
Dates must be in ISO 8601 format (e.g., 2025-10-03T15:00:00Z).

Filter by account

Get transactions for a specific account:

Combining filters

You can combine multiple filters to narrow down results:

Pagination

Handle large result sets with cursor-based pagination:
1

Get first page

Response:
2

Get next page

Use the nextCursor from the previous response:
3

Continue until done

Keep paginating while hasMore is true:
The maximum limit is 100 transactions per request. Default is 20.

Get a single transaction

Retrieve details for a specific transaction by ID:

Best practices

Always implement pagination when fetching transactions to avoid timeouts and memory issues:
For data that doesn’t change frequently (like completed transactions), implement caching:
Apply filters to get only the data you need:
Implement exponential backoff for rate limit errors:

Next steps