Jump to
Ctrl
+
/

Create UTXO Transaction Request from Vault

POST
/vaults/{vaultId}/{blockchain}/{network}/transaction-requests

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.


This is available only for UTXO-based protocols such as Bitcoin, Bitcoin Cash, Litecoin, etc. It is not available for Account-based protocols like Ethereum.

Path Parameters

blockchain string Required

Represents the specific blockchain protocol name, e.g Bitcoin.

network string Required

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.

vaultId string Required

Represents the sender's specific and unique Vault ID of the sender.

Query Parameters

context string Optional

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

context string Optional

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
feePriority string Required

Represents the fee priority of the automation, whether it is "slow", "standard" or "fast".

note string Optional

Represents an optional note to add a free text in, explaining or providing additional detail on the transaction request.

prepareStrategy string Optional

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).

recipients array Items (object) Required

Defines the destination of the transaction, whether it is incoming or outgoing.

address string Required

Defines the specific recipient address.

amount string Required

Represents the specific amount of the transaction's destination.

Response Schema

apiVersion string Required

Specifies the version of the API that incorporates this endpoint.

2024-05-09
requestId string Required

Defines the ID of the request. The requestId is generated by Vaultody and it's unique for every request.

601c1710034ed6d407996b30
context string Optional

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.

yourExampleString
data object Required
item object Required
feePriority string Required

Represents the fee priority of the automation, whether it is "slow", "standard" or "fast".

standard
note string Optional

Represents an optional note to add a free text in, explaining or providing additional detail on the transaction request.

yourAdditionalInformationhere
recipients array Items (object) Required

Information about each recipient of the transaction.

address string Required

Defines the specific destination address.

mmd963W1fECjLyaDCHcioSCZYHkRwjkhtr
amount string Required

Represents the amount received by the specific destination address .

0.00123
totalTransactionAmount string Required

Represents the total amount sent.

0.001
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.

6017dd02a309213863be9e55
transactionRequestStatus string Required

Defines the status of the transaction, e.g. "created".

created
Was this page helpful?
Yes
No
Powered by
Language
URL

{
    "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"
        }
    }
}