Create an HD address

Derive and register an HD address for the vault on a chain. Without a derivationPath, the next unused index is used. If an address already exists at the path, it is returned. Returns 400 on chains that do not support HD addresses, such as io.chain.

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.

Body Params
string
^m(\/\d+)+$

BIP-44 style HD derivation path of the form m/<n>/<n>/..., with unhardened numeric segments only. A hardened segment (', h or H suffix) returns 400. Where the field is optional and omitted, the vault base address is used.

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