Through this endpoint users can create a new transaction request from the entire Wallet instead from just a specific address. This endpoint can generate transactions from multiple to multiple addresses.
Represents the specific blockchain protocol name, e.g Bitcoin.
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 test network.
Represents the sender's specific and unique Vault ID of the sender.
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.
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.
Represents the fee priority of the automation, whether it is "slow", "standard" or "fast".
Represents an optional note to add a free text in, explaining or providing additional detail on the transaction request.
Refers to a model of a UTXO spending strategy, where customers can choose how to spend their transaction outputs from multiple Bitcoin addresses. Two options available - "minimize-dust" (select lower amounts from multiple addresses) or "optimize-size" (select higher amounts from less addresses).
Defines the destination of the transaction, whether it is incoming or outgoing.
Defines the specific recipient address.
Represents the specific amount of the transaction's destination.
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.
Represents the fee priority of the automation, whether it is "slow", "standard" or "fast".
Represents an optional note to add a free text in, explaining or providing additional detail on the transaction request.
Information about each recipient of the transaction.
Defines the specific destination address.
Represents the amount received by the specific destination address .
Represents the total amount sent.
Represents a unique identifier of the transaction request (the request sent to make a transaction), which helps in identifying which callback and which referenceId
concern that specific transaction request.
Defines the status of the transaction, e.g. "created".
cb233681a8ee35665296c1824c1f67bc46691788
PSqeqRLap8rBc/wogNU1DeGGUPb2VyVtg6GiBOaBnYQ=
1681885776
zYgKeueoOq
{
"context": "yourExampleString",
"data": {
"item": {
"feePriority": "standard",
"note": "yourAdditionalInformationhere",
"prepareStrategy": "minimize-dust",
"recipients": [
{
"address": "2MtzNEqm2D9jcbPJ5mW7Z3AUNwqt3afZH66",
"amount": "0.125"
}
]
}
}
}
{
"apiVersion": "2024-05-09",
"requestId": "601c1710034ed6d407996b30",
"context": "yourExampleString",
"data": {
"item": {
"feePriority": "standard",
"note": "yourAdditionalInformationhere",
"recipients": [
{
"address": "mmd963W1fECjLyaDCHcioSCZYHkRwjkhtr",
"amount": "0.00123"
}
],
"totalTransactionAmount": "0.001",
"transactionRequestId": "6017dd02a309213863be9e55",
"transactionRequestStatus": "created"
}
}
}