Cost: 1 credit per call
Interactive Playground: Test this endpoint in the API Playground. Get your API key at data.octav.fi
Endpoint
Required Parameters
Comma-separated list of wallet addressesMultiple addresses:
Number of transactions per page
- Minimum: 1
- Maximum: 250
- Recommended: 10-50 for optimal performance
Pagination offset (0-based)
Optional Parameters
Search & Filter
Full-text search in transaction assets
Searches across:
- Token symbols
- Token names
- Contract addresses
- Transaction descriptions
Filter by interacting addresses (comma-separated)
Shows only transactions where these addresses are involved:
Filter by transaction types (comma-separated type keys)See Transaction TypesCommon types:
SEND- Token transfers outRECEIVE- Token transfers inSWAP- Token swapsDEPOSIT- DeFi depositsWITHDRAW- DeFi withdrawalsSTAKE- Staking operationsCLAIM- Reward claimsAPPROVE- Token approvals
Exclude spam transactions
Sorting & Date Range
Sort order by timestamp
DESC- Newest first (recommended)ASC- Oldest first
Start date in ISO 8601 format
End date in ISO 8601 format
NFT Filters
Filter by NFT token ID
Response
Transaction Object
Transaction hash
Transaction timestamp in seconds since epoch
Blockchain information
key: Chain identifiername: Chain display name
Address initiating the transaction
Recipient address
Transaction type (DEPOSIT, WITHDRAWAL, SWAP, etc.)
Protocol information (if applicable)
key: Protocol identifiername: Protocol display name
Sub-protocol information (if applicable)
key: Sub-protocol identifiername: Sub-protocol name
Transaction value in native asset
Transaction value in USD
Fees paid in native asset
Fees paid in USD
Assets received in the transaction
Assets sent out in the transaction
Smart contract function called
Realized profit/loss for the transaction (if available, otherwise “N/A”)
Detailed fee breakdown
Example Request
Example Response
View Full Response
View Full Response
Use Cases
- Transaction History
- Filter by Type
- Search Transactions
- Date Range Query
- Fee Analysis
Display transaction history with pagination:
Pagination Best Practices
Efficient Pagination
Efficient Pagination
Use appropriate page sizes:
- Small pages (10-20): Fast response, more requests
- Medium pages (50-100): Balanced approach (recommended)
- Large pages (200-250): Fewer requests, slower response
Handling Large Histories
Handling Large Histories
For addresses with many transactions:
-
Use filters to reduce results:
- Filter by date range
- Filter by transaction type
- Filter by specific networks
-
Process in batches:
-
Implement caching:
- Cache transaction pages locally
- Only fetch new transactions since last sync
- Use
startDateto fetch only recent data
Error Responses
400 Bad Request
400 Bad Request
Invalid parameters provided.Common causes:
- Missing required parameters (
addresses,limit,offset) - Invalid parameter values
- Invalid date format
404 Not Found
404 Not Found
Address has more than 100,000 transactions.Solution: Contact support for assistance with high-volume addresses
401 Unauthorized
401 Unauthorized
402 Payment Required
402 Payment Required