Skip to main content

Overview

The Transfers suite provides access to all token transfer events produced by the TokenTransfersEngine via a single unified endpoint. Use the optional transfer_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

Parameter Conventions

number
required
Target EVM network. See Chain for supported values.
number
Starting block number (inclusive). Use with to_block.
number
Ending block number (inclusive). Use with from_block.
string
Starting timestamp (ISO-8601). Use with to_timestamp; mutually exclusive with block range.
string
Ending timestamp (ISO-8601). Use with from_timestamp.
string
Filter by sender address (hex, 20 bytes, no 0x prefix).
string
Filter by recipient address (hex, 20 bytes, no 0x prefix).
string
Filter by token contract (hex, 20 bytes). For native endpoint, omit or leave unset.
number
default:"250"
Page size; max 1000. Stays under ~10 MB when combined with narrow ranges.
string
Pagination cursor from a previous response.

Usage Guidance

  • Filter by type — Pass transfer_type as integer codes (0=native_tx, 1=native_internal, 2=erc20, 3=erc721, 4=erc1155) to narrow results to a specific asset kind in a single request. See the TransferType enumeration.
  • Narrow by address — Use from_address / to_address and optionally token_address to reduce payload and cost.
  • Join with entities — Use token_address with ERC-20, ERC-721, or ERC-1155 token metadata for symbols and decimals.

Common Patterns

ERC-20 transfers for a wallet:
NFT (ERC-721) transfers for a collection:
Native ETH only (no token contract):
All transfer types in one request:

Dataset & Relationships

See Also

Last modified on March 31, 2026