Get user wallet activity (deposits, withdrawals, transfers)
Changed onImmutable log of on-chain events that affected the wallet's vault position. Each row is a frozen-in-time record; rows never mutate after emission.
?vault_id= narrows to one vault; omitted = activity across every vault the wallet has touched, scoped to the Gauntlet-curated vault set (listed vaults by default, include_hidden=true widens to hidden vaults; disabled vaults never appear). Each row echoes its vault_id so wallet-wide consumers can distinguish per-vault activity.
Async deposit/redeem lifecycles emit multiple rows (one at request time with status=pending, a later one with status=settled or refunded). Consumers correlate them via request_hash to follow a single action across rows. Sync flows emit one row directly in the settled state.
Pagination is cursor-only. Default order is desc (newest first). Default page size 100, max 1000.
Request
- Base URL: https://api.gauntlet.xyz
- URL: https://api.gauntlet.xyz/v1/users/{wallet_address}/activity
- Auth: none declared
Path parameters
Ethereum wallet address
Query parameters
CAIP-10 vault identifier. Optional — omit for wallet-wide activity across every vault the wallet has touched.
Opaque cursor from previous meta.next_cursor.
Page size (1–1000, default 100).
Sort direction: desc (default) or asc.
Wallet-wide feeds only: include activity in hidden (enabled but unlisted) vaults alongside visible ones. Activity in disabled vaults is never returned. Ignored when vault_id is set.
Response
User wallet activity
Changes
- info
added the optional property
/to the response with the status
- info
- info
added the new optional
queryrequest parameterinclude_hidden - info
added the optional property
////////to the response with the status - info
added the optional property
/to the response with the status
- info