Create UTXO Transaction Request from Vault
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.
Path Parameters
-
Requiredblockchain string
Represents the specific blockchain protocol name, e.g Bitcoin.
-
Requirednetwork string
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.
-
RequiredvaultId string
Represents the sender's specific and unique Vault ID of the sender.
Query Paramaters
-
Optionalcontext 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.
Request Body Schema application/json
-
Optionalcontext 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. -
Requireddata object
-
Requireditem object
-
RequiredfeePriority string
Represents the fee priority of the automation, whether it is "slow", "standard" or "fast".
-
Optionalnote string
Represents an optional note to add a free text in, explaining or providing additional detail on the transaction request.
-
OptionalprepareStrategy string
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).
-
Requiredrecipients array
items (object)Defines the destination of the transaction, whether it is incoming or outgoing.
-
Requiredaddress string
Defines the specific recipient address.
-
Requiredamount string
Represents the specific amount of the transaction's destination.
-
-
-
Response Schema
Content Type: application/json
The resource has been successfully created.
Object :
-
RequiredapiVersion string
Specifies the version of the API that incorporates this endpoint.
Example : 2024-05-09 -
RequiredrequestId string
Defines the ID of the request. The
requestId
is generated by Vaultody and it's unique for every request.Example : 601c1710034ed6d407996b30 -
Optionalcontext 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.Example : yourExampleString -
Requireddata object
-
Requireditem object
-
RequiredfeePriority string
Represents the fee priority of the automation, whether it is "slow", "standard" or "fast".
Example : standard -
Optionalnote string
Represents an optional note to add a free text in, explaining or providing additional detail on the transaction request.
Example : yourAdditionalInformationhere -
Requiredrecipients array
Information about each recipient of the transaction.
-
Requiredaddress string
Defines the specific destination address.
Example : mmd963W1fECjLyaDCHcioSCZYHkRwjkhtr -
Requiredamount string
Represents the amount received by the specific destination address .
Example : 0.00123
-
-
RequiredtotalTransactionAmount string
Represents the total amount sent.
Example : 0.001 -
RequiredtransactionRequestId string
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.Example : 6017dd02a309213863be9e55 -
RequiredtransactionRequestStatus string
Defines the status of the transaction, e.g. "created".
Example : created
-
-