Through this endpoint you can list HD wallet's UTXOs (Unspent Transaction Outputs) by providing extended public key of an already synced HD wallet.
Represents the specific blockchain protocol name, e.g. Ethereum, Bitcoin, etc.
Defines the account extended publicly known key which is used to derive all child public keys.
Represents the name of the blockchain network used; blockchain networks are usually identical as technology and software, but they differ in data, e.g. - "mainnet" is the live network with actual data while network like "testnet" is a test network.
In batch situations the user can use the context to correlate responses with requests. This property is present regardless of whether the response was successful or returned as an error. context
is specified by the user.
The way how the HD walled derives, for example when the type is ACCOUNT, it derives change and receive addresses while when the type is BIP32 it derives directly.
Defines how many items should be returned in the response per page basis.
The starting index of the response items, i.e. where the response should start listing the returned items.
Specifies the version of the API that incorporates this endpoint.
Defines the ID of the request. The requestId
is generated by Crypto APIs and it's unique for every request.
In batch situations the user can use the context to correlate responses with requests. This property is present regardless of whether the response was successful or returned as an error. context
is specified by the user.
Defines how many items should be returned in the response per page basis.
The starting index of the response items, i.e. where the response should start listing the returned items.
Defines the total number of items returned in the response.
Represents the public address, which is a compressed and shortened form of a public key.
Defines a data which tells a Hierarchical Deterministic wallet how to derive a specific key within a tree of keys.
Represents the UTXO amount value.
The way how the HD walled derives, for example when the type is ACCOUNT, it derives change and receive addresses while when the type is BIP32 it derives directly.
Represents the output index. It refers to the UTXO sequence in the transaction outputs (vout).
Represents if the UTXO has been used from another unconfirmed transaction. If it is - the value will be "false".
Represents the state of the transaction whether it is confirmed or not confirmed.
Represents the reference id of the record. It may be used for the startingAfter pagination attribute.
Represents the unique identifier of a transaction, i.e. it could be transactionId in UTXO-based protocols like Bitcoin, and transaction hash in Ethereum blockchain.
API Key
{
"apiVersion": "2023-04-25",
"requestId": "601c1710034ed6d407996b30",
"context": "yourExampleString",
"data": {
"limit": 50,
"offset": 0,
"total": 100,
"items": [
{
"address": "muZxmnQiz8gZgpYmUoTHpD2CFTHWYEjTwB",
"addressPath": "m/0/5",
"amount": "0.0005",
"derivation": "ACCOUNT",
"index": 1,
"isAvailable": true,
"isConfirmed": true,
"referenceId": "5b1ea92e584bf50020130615",
"transactionId": "06af8234602b97f497496039a6eb99810db1287ce8aa3c501894dcd03bd4e544"
}
]
}
}