userNonFundingLedgerEvents
Stream specific users' non funding ledger events
Every live data message includes both routing identifiers with the same value:
{"type": "userNonFundingLedgerEvents", "channel": "userNonFundingLedgerEvents"}Other payload fields are omitted above. Existing clients may continue routing on either field.
Subscribe
{
"type": "subscribe",
"subscription": {
"type": "userNonFundingLedgerEvents",
"addresses": ["0x574bafce69d9411f662a433896e74e4f153096fa"],
"dex": "dex_name", // optional; "main" (alias "hyperliquid") = native dex, or a HIP-3 dex name. Leave out for all events
"addStakingEvents": bool // optional false by default
}
} Unsubscribe
{
"type": "unsubscribe",
"subscription": {
"type": "userNonFundingLedgerEvents",
"addresses": ["0x574bafce69d9411f662a433896e74e4f153096fa"],
"dex": "dex_name", // optional; "main" (alias "hyperliquid") = native dex, or a HIP-3 dex name. Leave out for all events
"addStakingEvents": bool // optional false by default
}
}userNonFundingLedgerEvents data format
Each ledger event represents a balance change from a specific user's perspective. Key fields:
user: The primary address this event affects (always matches one of your subscribed addresses)
role: The user's role in the event:
"user"- Single-party events (deposits, withdrawals, account class transfers, liquidations)"sender"- User is sending funds to another party"receiver"- User is receiving funds from another party
counterparty: The other address involved in transfers (only present for bilateral transactions)
counterpartyDex: The DEX/chain of the counterparty (omitted when "hyperliquid")
Important: For transfers, you only receive the perspective where user matches your subscribed address. For example, if Alice sends funds to Bob and you're subscribed to Alice, you receive the sender perspective with Alice as user and Bob as counterparty. You do NOT receive Bob's receiver perspective unless you're also subscribed to Bob's address.
Each event contains a timestamp, hash, and delta fields describing the ledger change. Events are batched per block.
Examples
Error messages:
Common errors
Last updated