Unified transfers
Heimdahl.xyz REST API Transfer Tutorial
This tutorial demonstrates how to use our Transfers REST API to retrieve token transfer data across different blockchains, networks, and addresses.
API Endpoint
Note: This API requires authentication using a Bearer token.
Path Format
The path follows one of these two patterns:
{chain}.{network}.{token}.{from}.{to}.all
{chain}.{network}.{token}.{wallet}.all
Where:
chain
: Blockchain (ethereum, polygon, base, binance, solana, arbitrum, tron)network
: Network type (mainnet, testnet, goerli, etc.)token
: Token symbol (USDT, USDC, WETH, etc.)from
: Sender address (0x...)to
: Recipient address (0x...)wallet
: Single wallet to query (either as sender or receiver)The final parameter is currently set to
all
which is reserved for filter by amount bucket it belonss to (small, large or whale depending on particular tokens circulating supply)
Example Usage
Basic command structure
Examples by Chain and Token
USDC Examples
Ethereum
Path Format Note
The current version of the API uses all
for the transfer size bucket parameter:
All paths end with
.all
to indicate all transfer sizes
Response Format
The API returns transfer data in JSON format. Each transfer contains the following information:
The response includes these key fields:
timestamp
: Unix timestamp of the transferfrom_address
: Sender addressto_address
: Recipient addressamount
: Transfer amount (in token units)token_address
: Address of the token contractsymbol
: Token symbol (USDC, USDT, WETH, etc.)chain
: Blockchainnetwork
: Network type (mainnet, testnet, etc.)tx_hash
: Transaction hashdecimals
: Number of decimal places the token usesposition
: Block position
Last updated