API reference
Vaultody
POST
/vaults/{vaultId}/transaction-requests/multiple-transfer
Create Multiple Transfer
Through this endpoint users can make UTXO-based transactions.
To have an operational callback subscription, you need to first verify a domain for the Callback URL. Please see more information on Callbacks here.
Vaultody will notify the user only when the event occurs. There are cases when the specific event doesn't happen at all, or takes a long time to do so. A callback notification will not be sent if the event does not or cannot occur, or will take long time to occur.
Path parameters
vaultId
string
required
Sender's Vault ID.
Query parameters
context
string
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.
Body parameters application/json
context
string
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.
data
object
required
item
object
required
assetId
string
required
e.g. 6523e058a06ebf1322d7dd6f
Unique internal identifier of the blockchain asset involved in the transaction.
feePriority
string
required
e.g. slow
Fee priority of the transaction - slow, standard, fast.
slow
standard
fast
gross
boolean
Optional boolean. When true, the specified amount is gross (fee is deducted from it). Default is false (net amount).
maxFee
string
e.g. 0.003
The maximum allowable transaction fee set by the client. If the actual transaction fee exceeds this value, the transaction will not be processed.
note
string
required
e.g. yourAdditionalInformationhere
Represents an optional note to add a free text in, explaining or providing additional detail on the transaction request.
prepareStrategy
string
required
e.g. optimize-size
Refers to a model of a UTXO spending strategy, where customers can choose how to spend their transaction outputs from multiple addresses.
minimize-dust
optimize-size
recipients
object[]
required
Destinations for the transaction.
address
string
required
e.g. bc1qut6n59lceee7s94g5qme08yzu8evd2yfjuuu...
Destination address.
amount
string
required
e.g. 0.001
Destination amount.
vaultAccountId
string
required
e.g. 6913471c6b2794841dc8fb81
Unique identifier of the Vault Account.
Response
Returns 201 the resource has been successfully created.
apiVersion
string
required
Specifies the version of the API that incorporates this endpoint.
requestId
string
required
Defines the ID of the request. The `requestId` is generated by Vaultody and it's unique for every request.
context
string
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.
data
object
required
item
object
required
amountUnit
string
required
Amount unit.
feePriority
string
required
Fee priority of the transaction - slow, standard, fast.
slow
standard
fast
gross
boolean
Whether the amount is gross (fee deducted from amount).
maxFee
string
The maximum allowable transaction fee set by the client. If the actual transaction fee exceeds this value, the transaction will not be processed.
note
string
required
Transaction note with additional details.
prepareStrategy
string
required
UTXO prepare strategy used.
minimize-dust
optimize-size
recipients
object[]
required
Destinations of the transaction
address
string
required
Address of the destination.
amount
string
required
Defines the amount sent to the destination address.
amountUnit
string
required
Defines the unit of the received amount for the address, e.g. BTC, LTC.
convertedAmountToUSD
string
required
Amount calculated in USD.
totalTransactionAmount
string
required
Total amount of the transaction.
transactionRequestId
string
required
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.
transactionRequestStatus
string
required
Defines the status of the transaction, e.g. "created".
created
await-approval
pending
prepared
signed
broadcasted
success
failed
rejected
mined
mined-with-errors
await-approval-l2