Enhanced Transactions API
Transform complex Solana blockchain transactions into human-readable data with Helius Enhanced Transactions API. Parse transaction details, fetch history, and understand on-chain activity without manual decoding.
Parse Transaction(s)
Parse individual or multiple transactions to get human-readable data
Transaction History
Get historical transaction data for any address
Quick Reference:
/v0/transactions
- Parse individual or multiple transaction signatures/v0/addresses/{address}/transactions
- Get transaction history for an address- Filter by transaction type using the
type
parameter (e.g.,NFT_SALE
,SWAP
,TRANSFER
)
Important Limitations:
- Enhanced Transaction API V1 won’t be updated while we are working on V2
- We only parse NFT, Jupiter, and SPL-related transactions
- Do not rely on these parsers for DeFi or non-NFT, Jupiter, and SPL transactions
Overview
The Enhanced Transactions API transforms complex Solana transactions into human-readable data. Instead of dealing with raw instruction data and account lists, you get structured information about:
- What happened in the transaction (transfers, swaps, NFT activities)
- Which accounts were involved
- How much SOL or tokens were transferred
- Timestamps and other metadata
Getting Started
Parse Individual Transactions
Parse one or more transaction signatures or raw transaction data with a single API call:
API Reference
View detailed documentation for parsing transactions
Fetch Transaction History for an Address
Retrieve transaction history for any Solana address:
API Reference
View detailed documentation for transaction history
Handling Incomplete Transaction Sets
Occasionally, history endpoint may return an incomplete set of transactions due to internal timeouts during data retrieval.
To mitigate this issue:
- First, call
getSignaturesForAddress
to retrieve a batch of transaction signatures - Next, use the
/v0/transactions
endpoint with the received signatures - If any transactions are missing from the response, you can retry fetching these specific transactions
Common Use Cases
Complete Pagination Example
For high-volume addresses, implement pagination to fetch all transactions:
Filter Transactions by Type
Get only specific transaction types, such as NFT sales:
API Reference
Query Parameters
Parameter | Description | Default | Example |
---|---|---|---|
limit | Number of transactions to return | 10 | &limit=25 |
before | Fetch transactions before this signature | - | &before=sig123... |
until | Fetch transactions until this signature | - | &until=sig456... |
type | Filter by transaction type | - | &type=NFT_SALE |
commitment | Commitment level | finalized | &commitment=confirmed |
Response Example
Enhanced transaction responses include structured data with human-readable descriptions:
Best Practices
Error Handling
Implement proper error handling and retries for production applications
Rate Limiting
Use pagination and caching strategies to avoid hitting rate limits
Error Handling
Always implement proper error handling in your code:
Rate Limiting Considerations
To avoid hitting rate limits when working with the API:
- Implement pagination for large datasets
- Cache responses when appropriate
- Add exponential backoff for retries
- Consider upgrading your API plan for high-volume applications
For high-traffic applications, consider implementing a caching layer with Redis or similar technology to minimize redundant API calls.