Monitor an address

Start monitoring a vault address so io.vault tracks its balances and transactions. Monitoring an address that is already monitored has no effect. Returns 400 on chains that always monitor their addresses, such as io.chain and Liquid.

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Path Params
uuid
required

Vault ID. You create vaults with io.sign (POST /v2/vaults). A malformed ID returns 400; an unknown ID returns 404.

string
required

Chain family: evm (Ethereum and EVM chains), svm (Solana), tvm (Tron), utxo (Bitcoin and other UTXO chains), or xrp (XRP Ledger). The chain must belong to it. Not every endpoint accepts every ecosystem; see the operation description.

string
required

Chain alias, such as ethereum, avalanche-c, solana, tron, bitcoin or ripple, not a numeric chain ID. GET /v2/treasury/chains lists the canonical aliases of the chains you can use, and includes testnets with includeTestnets=true. Older aliases such as btc are also accepted.

string
required
length ≥ 1

On-chain address in the format of the chain the request names, in the path or the body: EVM 0x hex, Solana base58, Tron T… base58, Bitcoin bc1… or legacy (testnets tb1…), XRP r….

Headers
string
length between 1 and 255

Key that makes this call safe to retry. Repeating the key with the same body returns the original response without running the operation again. Reusing the key with a different body is refused. Keys are scoped to you and this operation, so the same key on another operation does not collide. Keys expire some time after the original call completes. An empty or whitespace-only value is rejected. Maximum length: 255 characters.

Responses

Language
Credentials
Bearer
JWT
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json