Through this endpoint customers can obtain details on transactions by vault id.
The sepcific Vault ID.
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.
Defines the id of the previous listed record id from which the current list should start from.
Specifies the version of the API that incorporates this endpoint.
Defines the ID of the request. The requestId
is generated by Vaultody 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.
Defines the id of the previous listed record id from which the current list should start from.
Defines whether or not there are more elements available after this set.
The blockchain protoocl, e.g Bitcoin, Ethereum, Tron.
When this transaction was created.
The direction of the transaction in this Vault, incoming or outgoing transaction.
If this transaction has any tokens transfers.
The transaction ID in Vaultody, this is needed for pagination/load more functionality.
If this transaction has any Internal Transactions.
The block height this transaction was mined in.
The blockchain network e.g mainnet, testnet, sepolia.
Recipients are all addresses receive assets in this transaction.
The public address itself.
The address type, e.g deposit, smart.
The amount received.
If this address belongs to this Vault or not.
The label of the address.
The unit symbol e.g. BTC, TRX, BNB.
Senders are all addresses send assets in this transaction.
The public sender's address.
The address type , e.g. Deposit, Smart.
The amount sent.
If this address belongs to this Vault.
The address label.
The symbol, e.g BTC, TRX, BNB, ETH.
The status of the transaction.
The transaction fee details.
The transaction fee amount
The transaction fee symbol.
The blockchain transaction ID.
cb233681a8ee35665296c1824c1f67bc46691788
PSqeqRLap8rBc/wogNU1DeGGUPb2VyVtg6GiBOaBnYQ=
1681885776
zYgKeueoOq
{
"apiVersion": "2024-05-09",
"requestId": "601c1710034ed6d407996b30",
"context": "yourExampleString",
"data": {
"limit": 50,
"startingAfter": "5ca21f92cf5431000105d1a7",
"hasMore": true,
"items": [
{
"blockchain": "bitcoin",
"createdTimestamp": 1705399159,
"direction": "incoming",
"hasTokenTransfer": "false",
"id": "654ba3af9e8dd80901f17347",
"isInternal": "false",
"minedInBlockHeight": "1234324",
"network": "mainnet",
"recipients": [
{
"address": "TKGMSZh4Wf3pVB2gWkUqzU7vwGhRy4H245",
"addressType": "deposit",
"amount": "5.96124",
"isVaultAddress": "true",
"label": "Tron address",
"unitSymbol": "USDT"
}
],
"senders": [
{
"address": "TF5mtoWoahGhJiPU4BXXANPvL1kuRwrBoM",
"addressType": "",
"amount": "0.000001",
"isVaultAddress": "true",
"label": "",
"unitSymbol": "BTC"
}
],
"status": "completed",
"transactionFee": {
"amount": "5.96124",
"unitSymbol": "TRX"
},
"transactionId": "281a63d28ddf6d0d5d78090b7cdf3a8c0be95bbb296544943ef45d9dec44405d"
}
]
}
}