Overview
The Transfers suite provides access to all token transfer events produced by the TokenTransfersEngine via a single unified endpoint. Use the optionaltransfer_type filter to narrow results to a specific asset kind. The endpoint supports the same request shape (chain, block or time range, optional address filters, pagination) and returns a consistent record format with lineage fields.
Endpoint
| Endpoint | Summary | Transfer types |
|---|---|---|
POST /evm/transfers/token-transfers | All transfer types in one response; filter by transfer_type | native_tx, native_internal, erc20, erc721, erc1155 |
Parameter Conventions
Starting block number (inclusive). Use with
to_block.Ending block number (inclusive). Use with
from_block.Starting timestamp (ISO-8601). Use with
to_timestamp; mutually exclusive with block range.Ending timestamp (ISO-8601). Use with
from_timestamp.Filter by sender address (hex, 20 bytes, no
0x prefix).Filter by recipient address (hex, 20 bytes, no
0x prefix).Filter by token contract (hex, 20 bytes). For native endpoint, omit or leave unset.
Page size; max 1000. Stays under ~10 MB when combined with narrow ranges.
Pagination cursor from a previous response.
Usage Guidance
- Filter by type — Pass
transfer_type(erc20,erc721,erc1155,native_tx, ornative_internal) to narrow results to a specific asset kind in a single request. - Narrow by address — Use
from_address/to_addressand optionallytoken_addressto reduce payload and cost. - Join with entities — Use
token_addresswith ERC-20, ERC-721, or ERC-1155 token metadata for symbols and decimals.
Common Patterns
ERC-20 transfers for a wallet:Dataset & Relationships
- Dataset ID:
0304— Token transfers (data catalog) - Transfers → Transactions: Join on
(block_number, tx_index)to transactions - Transfers → Tokens: Join
token_addressto ERC-20, ERC-721, or ERC-1155 for metadata
See Also
- Token Transfers — Full endpoint reference
- Data catalog: Token Transfers — Schema and columns