API reference, Bridges & wallets

Bridge movements stream

The GET /v1/bridges answer (movements newest first, 24 h stats), pushed on subscribe, then when a movement of the route changes state.

WebSocket channel bridges.recent on wss://api.femtos.xyz/v1/ws

Parameters

Param	In	Example or values	Meaning
`route`	filter	`evm_elysium` (Elysium); `core_evm` (HyperCore, HyperEVM)	core_evm (HyperCore <> HyperEVM) or evm_elysium (HyperEVM <> Elysium)
`direction`	filter	(optional)	Direction (core_evm: evm_to_core, core_to_evm; evm_elysium: to_child, to_parent)
`token`	filter	(optional)	Token address (`hype` for native HYPE)
`limit`	filter	(optional)	Rows, newest first, default 100 (1..100)

Elysium

{"op":"subscribe","channel":"bridges.recent","filter":{"route":"evm_elysium"}}

HyperCore, HyperEVM

{"op":"subscribe","channel":"bridges.recent","filter":{"route":"core_evm"}}

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

Field	Type	Meaning
`snapshot: true`	object	the full GET /v1/bridges answer: the first frame, and any frame sent whole
`patch: true`	JsonPatch	with "patch": true on subscribe: the operations, in order, that turn the previous answer into this one
`billing`	medium	the snapshot a subscribe asks for counts as GET /v1/bridges (medium); every other frame by its bytes (1 credit per 48 KiB)

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.
Transfers by wallet GET /v1/transfers Elysium, HyperEVM
ERC-20 transfers sent and received by a wallet, newest first, filterable by token, direction, 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.