Transactions API
The Transactions API allows you to retrieve and manage transaction history. Every quote that is processed becomes a transaction with different statuses throughout its lifecycle.
List Transactions
Retrieve a paginated list of transactions with comprehensive filtering options. Use this endpoint to display transaction history, generate reports, or track transaction statuses.
Endpoint
Client API Endpoint: GET /api/v1/client/transactions/v2
Note: We recommend using the V2 endpoint (
/transactions/v2) as it provides enhanced payment tracking, smart currency mapping for crypto transactions, and more comprehensive transaction details.
Authentication
This endpoint requires HMAC authentication (Business API Key). Include your API key and signature in the request headers:
Note: For HMAC authentication details, see the Authentication guide.
Query Parameters
Transaction Types
DEPOSIT- Funds deposited into an accountWITHDRAWAL- Funds withdrawn from an accountEXCHANGE- Currency exchange between two currenciesTRANSFER- Transfer between usersDIRECT_EXCHANGE- Direct currency exchangeFEE- Fee transactions
Transaction Statuses
PENDING- Transaction is pending processingPROCESSING- Transaction is being processedCOMPLETED- Transaction completed successfullyFAILED- Transaction failedCANCELLED- Transaction was cancelled
Success Response (200 OK)
Response Fields
Error Responses
Example: cURL
Example: HTTP Request
Get Transaction By ID
Retrieve detailed information about a specific transaction, including all amounts, currencies, fees, status, and timestamps.
Endpoint
Client API Endpoint: GET /api/v1/client/transactions/v2/{id}
Authentication
This endpoint requires HMAC authentication (Business API Key). Include your API key and signature in the request headers:
Note: For HMAC authentication details, see the Authentication guide.
Path Parameters
Success Response (200 OK)
Returns the same transaction object structure as in the list endpoint, but for a single transaction:
Error Responses
Example: cURL
Example: HTTP Request
Use Cases
- Transaction History - Display user transaction history with pagination
- Status Tracking - Monitor transaction status changes (PENDING → PROCESSING → COMPLETED)
- Reporting - Generate reports filtered by date, type, status, or currency
- Reconciliation - Match transactions with external records using transaction references
- Analytics - Analyze transaction patterns, volumes, and success rates
- Audit Trail - Maintain detailed records of all financial transactions
Best Practices
- Use Pagination - Always implement pagination for large transaction lists
- Cache Results - Cache transaction details that don't change frequently
- Filter Efficiently - Use specific filters to reduce response size and improve performance
- Handle Errors - Implement proper error handling for 404 (not found) and 403 (forbidden) responses
- Store References - Keep transaction references and IDs for reconciliation purposes
- Poll for Updates - For pending transactions, poll the Get Transaction endpoint to check status updates
Time Filtering Tips
When using time_type, always provide the tz parameter:
TODAY- Transactions from today in the specified timezoneTHIS_WEEK- Transactions from the current weekTHIS_MONTH- Transactions from the current monthTHIS_YEAR- Transactions from the current yearRANGE- Usefromandtoparameters for custom date ranges
Example:
Next Steps
- Quotes API - Learn how quotes become transactions
- Webhooks - Set up webhooks to receive real-time transaction updates
- Virtual Wallets API - View virtual wallet balances and transaction history