API reference · Bridges & wallets

Transfers by wallet

ERC-20 transfers sent and received by a wallet, newest first, filterable by token, direction, size and time.

Not on HyperCore: HyperCore has no ERC-20 Transfer logs: an account’s transfers are on the wallet page and in the hc.ledger stream

GET https://api.femtos.xyz/v1/transfers

Parameters

Param	In	Example or values	Meaning
`layer`	query	`elysium` (Elysium); `hyperevm` (HyperEVM)	EVM layer
`address`	query	`<creator>` (Elysium); `<evmWallet>` (HyperEVM)	Transfers from / to this address (a named wallet's handle works too); token then optional
`direction`	query	`any`, `in`, `out`	With address: received, sent or both
`token`	query	(optional)	Token address (required without address)
`minUsd`	query	(optional)	With address: smallest amount × current token price, USD
`limit`	query	`20`	Rows
`cursor`	query	(optional)	Next page: `next_cursor` of the previous answer

Elysium

curl -H "Authorization: Bearer $FEMTOS_KEY" "https://api.femtos.xyz/v1/transfers?layer=elysium&address=<creator>&direction=any&limit=20"

HyperEVM

curl -H "Authorization: Bearer $FEMTOS_KEY" "https://api.femtos.xyz/v1/transfers?layer=hyperevm&address=<evmWallet>&direction=any&limit=20"

Key: Authorization: Bearer $FEMTOS_KEY. Get a free key, or with no browser through agent onboarding.

Field	Type	Meaning
`rows[]`	object	Newest first: {block, t, tx, logIndex, token, symbol, decimals, from, to, direction, amount, amountRaw, …}
`usdBasis`	current_price \| null	What usd / minUsd value the transfers at
`fromBlock`	int	First block of the window
`toBlock`	int	Last block of the window
`scanned`	int	Index rows read for this page (filters apply to them: at most 1000 per source per call)
`spamHidden`	int	Rows of spam tokens left out (includeSpam=true shows them)
`next_cursor`	string \| null	Opaque cursor of the next page; null when nothing is left in the window. A filtered page can hold fewer rows than limit, even none: keep paging while next_cursor is not null

Next page: cursor = the next_cursor of the previous answer, the same on every list (pagination).

Cross-layer wallet GET /v1/wallet/{address} Elysium, HyperCore, HyperEVM
One address (or a named wallet's handle) on HyperCore, HyperEVM and Elysium, plus its latest events.
Wallet stream WS wallet Elysium, HyperCore, HyperEVM
Every event of the three layers touching one address.
Swaps by wallet GET /v1/trades Elysium, HyperEVM
Every swap a wallet sent (or a pool’s, a token’s), newest first, filterable by token, side, size and time.
Ledger stream WS hc.ledger HyperCore
Deposits, withdrawals, transfers and other non-trade balance moves.
Bridge movements GET /v1/bridges Elysium, HyperCore, HyperEVM
Matched HyperCore ↔ HyperEVM transfers with 24 h stats.
Bridge stream WS elysium.bridge · bridge.transfers Elysium, HyperCore, HyperEVM
Each HyperCore ↔ HyperEVM transfer, initiated then completed.
Bridge coverage GET /v1/bridges/coverage HyperCore, HyperEVM
Every HyperCore ↔ HyperEVM leg since our data starts, paired with its other leg: matched share per direction and token, why the others are not, latency.