Skip to main content
GET
Get wallet transactions

Authorizations

Authorization
string
header
required

Client API Key or Client Session Token (CST). Pass as a Bearer token in the Authorization header.

Path Parameters

chain
string
required

The blockchain chain identifier. Use either a friendly name or CAIP-2 format. When using CAIP-2 format in URLs, ensure the colon (:) is URI-encoded as %3A.

Supported chains:

  • ethereum (eip155:1)
  • sepolia (eip155:11155111)
  • base (eip155:8453)
  • base-sepolia (eip155:84532)
  • polygon (eip155:137)
  • polygon-mumbai (eip155:80001)
  • celo (eip155:42220)
  • celo-alfajores (eip155:44787)
  • monad (eip155:143)
  • monad-testnet (eip155:10143)
  • solana (solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp)
  • solana-devnet (solana:EtWTRABZaYq6iMfeYKouRu166VU2xqa1)
  • tron (tron:mainnet)
  • tron-nile (tron:nile)
  • tron-shasta (tron:shasta)
  • stellar (stellar:pubnet)
  • stellar-testnet (stellar:testnet)
  • bitcoin-segwit (bip122:000000000019d6689c085ae165831e93-p2wpkh)
  • bitcoin-segwit-testnet (bip122:000000000933ea01ad0ee984209779ba-p2wpkh)
  • bitcoin-p2wpkh (bip122:000000000019d6689c085ae165831e93-p2wpkh)
  • bitcoin-p2wpkh-testnet (bip122:000000000933ea01ad0ee984209779ba-p2wpkh)

Query Parameters

limit
integer
default:50

Maximum number of transactions to return. Defaults to 50. Capped at 1000 for EVM chains and 15 for Solana.

offset
integer
default:0

Number of transactions to skip (default 0).

order
enum<string>

Sort order for transactions.

Available options:
asc,
desc
address
string

Override the wallet address used for the query (EVM only). Must match the client's known EOA or smart contract address.

userOperations
enum<string>
default:include

Filter for ERC-4337 UserOperations (EVM only). Defaults to include.

  • include — return both regular transactions and UserOperations
  • only — return only UserOperations
  • exclude — return only regular transactions
Available options:
include,
only,
exclude

Response

Transactions retrieved successfully

Response format varies by chain:

  • Solana: transactions are SolanaTransactionDetails objects (legacy format with signature, blockTime, tokenMint, and nested transactionDetails).
  • All other chains: transactions are TransactionHistoryItem objects (unified format with hash, from, to, value, blockNumber, blockTimestamp, status, chainId). Solana will be migrated to the unified format in a future release.
data
object
metadata
object