A blockchain transfer or more accurately a token transfer, is when a token (on a blockchain like Ethereum) is transferred in a transaction. For example, when sending SHIB from one address to another, this would be a token transfer.


The Amberdata API's allow you to query token transfers multiple ways including from an address, block, transaction hash or just from a particular token like DAI. This way you, the user, can determine how you want to query transfer data. From the highest level (the block) to the most granular (the transaction hash), Amberdata lets you query as much or as little data as you need. The ability to only view a particular token like DAI (or any other token on the chains we support), will allow you to analyze just that particular token. For example, it you wanted to see all the DAI transfers for particular time period and compare them with USDC transfers from the same time period, the token transfers endpoint in the Token section can easily do this for you.

API Endpoints

/address-token transfers
/blocks-token transfers
/tokens-token transfers
/transactions-token transfers


Our Transfers endpoints found throughout the different On-Chain namespaces are available via REST API, WebSockets or JSON RPC. The list of supported Blockchain networks can be found in the API Documentation here.

Since we maintain our own nodes, we have every event from the genesis block forward which enables us to provide complete historical datasets for most of the chains we support.

Frequently Asked Questions

Which tokens can I see transfer data for on Ethereum??

  • We currently support ERC-20, 721, 777, 884, 998 and 1155.

What additional data do you show in the transfers endpoint responses?

  • Depending on the endpoint, the response can include the token name, symbol, timestamp, token type, to/from addresses and much more.