Skip to main content
GET
Get wallet transactions

Authorizations

Authorization
string
header
required

To test endpoints here, paste your API key from the Dashboard into the username field and leave the password empty.

Headers

X-Env
enum<string>

Custom header that allows you to get data for testnets.

Available options:
testnet

Path Parameters

address
string
required

Address of the wallet. Must be a valid EVM or Solana address. Returns 400 if the address is not one Zerion tracks, such as a token contract, router or exchange hot wallet. Smart-contract wallets like Safe and ERC-4337 accounts are tracked as normal.

Query Parameters

currency
enum<string>
default:usd

Denominated currency value of returned prices

Available options:
eth,
btc,
usd,
eur,
krw,
rub,
gbp,
aud,
cad,
inr,
jpy,
nzd,
try,
zar,
cny,
chf
page
object

Pagination parameters

filter[search_query]
string

Query for a full-text search.

Required string length: 2 - 64
Example:

"Trade"

filter[operation_types]
enum<string>[]

Return only transactions with specified types (comma-separated list). See the operation type schema for the full list of values.

Type of the transaction operation. This field indicates the primary action performed in the transaction.

Possible values and their meanings:

  • approve - Grant permission to a smart contract to access and spend tokens on behalf of the wallet
  • bid - Place a bid in a prediction market
  • burn - Destroy tokens permanently, reducing the total token supply
  • claim - Claim earned rewards, airdrops, or vested tokens from a protocol
  • delegate - Delegate tokens or voting power to another address
  • deploy - Deploy a new smart contract onchain
  • deposit - Deposit assets into a protocol (e.g., lending pool, liquidity pool, vault)
  • execute - Execute a smart contract function or complex interaction that doesn't fit other specific types
  • mint - Create new tokens, increasing the total token supply
  • receive - Receive tokens from another wallet address
  • revoke - Revoke previously granted token spending permissions from a smart contract
  • revoke_delegation - Revoke a previously delegated token or voting power
  • send - Send tokens to another wallet address
  • trade - Exchange or swap assets (e.g., on a DEX)
  • withdraw - Withdraw assets from a protocol (e.g., from lending pools, liquidity pools, or vaults)
Available options:
approve,
bid,
burn,
claim,
delegate,
deploy,
deposit,
execute,
mint,
receive,
revoke,
revoke_delegation,
send,
trade,
withdraw
filter[asset_types]
enum<string>[]

Return only transactions that contain specified asset types (comma-separated list).

Type of concrete asset.

Available options:
fungible,
nft
filter[chain_ids]
string[]

Return only transactions from specified chains (comma-separated list). Only chains reporting supports_transactions in the flags of GET /v1/chains/ are accepted here. Naming a chain that fails that gate returns 400 rather than an empty result, with detail reading chain <id> does not support transactions (for example chain tron does not support transactions). A chain of the wrong network family for the address is rejected the same way, with does not support this wallet address type. When the filter is omitted, chains that fail the gate are left out of data silently, with no error and no meta signal.

filter[fungible_ids]
string[]

Return only transactions with fungibles with specified ids (comma-separated list).

filter[min_mined_at]
string

Return only transactions since specific date. Timestamp in milliseconds.

Required string length: 13
Example:

"1688842525735"

filter[max_mined_at]
string

Return only transactions until specific date. Timestamp in milliseconds.

Required string length: 13
Example:

"1694192535967"

filter[trash]
enum<string>
default:no_filter

Filter transactions based on the is_trash flag. If no flag is specified, then no_filter is applied.

Available options:
only_trash,
only_non_trash,
no_filter
filter[fungible_implementations]
string[]

Specify implementations of fungible tokens as a comma-separated list of chain:address pairs.

Example format: ethereum:0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48,polygon:0x123456789abcdef123456789abcdef123456789

Each item consists of a chain_id and an address, separated by a colon (:). Multiple pairs can be provided using commas (,).

Response

Response for requested list of transactions

data
object[]
required