Through this endpoint customers can prepare an unsigned UTXO-based transaction from a single funding address. The service selects the necessary UTXOs from that address, estimates the fee by the chosen priority, and returns the unsigned inputs (with the sighashes to sign) and outputs. The funding address pays the fee and receives the change.
Represents the specific blockchain protocol name, e.g. Bitcoin.
Represents the name of the blockchain network used; e.g. "mainnet" is the live network with actual data while "testnet" is a test network.
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 an optional free-text note attached to the transaction request (embedded as OP_RETURN data).
Represents the earliest time or block a transaction may be added to the blockchain.
Represents the single funding address. It funds the outputs, pays the transaction fee and receives the change.
Object array representation of the transaction's recipients. Each item specifies a recipient address and the amount it should receive.
Represents the specific recipient's address.
Represents the specific amount the recipient receives, in the main denomination (BTC).
Specifies the fee details for the transaction.
Represents the fee priority of the transaction, i.e. how quickly it should be mined.
Represents an exact fee amount to use, in the main denomination. When set, it overrides the priority-based estimate.
Represents the UTXO-selection strategy.
Represents whether the transaction is replaceable (BIP-125 Replace-By-Fee).
Specifies the version of the API that incorporates this endpoint.
Defines the ID of the request. The requestId is generated by Crypto APIs 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.
The total fee of the transaction.
The total fee amount, in the main denomination.
The denomination of the fee amount.
The fee per byte used to compute the total fee.
The fee-per-byte amount, in the main denomination.
The denomination of the fee-per-byte amount.
The estimated size of the transaction in bytes.
The transaction's version number.
The transaction's locktime.
The optional free-text note attached to the transaction.
Object array of the transaction's selected inputs, each with the hash (sighash) that must be signed.
The address the input is spent from.
The index of the referenced output in the source transaction.
The value of the input, in satoshis.
The locking script of the referenced output.
The hash that must be signed for this input.
The id of the source transaction of the input.
Object array of the transaction's outputs (recipients plus the change back to the sender).
The recipient (or change) address of the output.
The value of the output, in satoshis.
The locking script of the output.
| Blockchain protocol | Credits for 1 Results |
| Default Cost | 530 |
| Bitcoin | 520 |
| Litecoin | 583 |
| Dogecoin | 583 |
| Dash | 583 |
| Zcash | 689 |
| Bitcoin Cash | 689 |
API Key
{
"context": "yourExampleString",
"data": {
"item": {
"additionalData": "yourAdditionalDataHere",
"locktime": 0,
"fromAddress": "tb1q7cer5fh3w656jpe30gudzjg05j0kmd48jwxhzh",
"recipients": [
{
"address": "tb1qsf7w5q7pnrumkm6r9zct4ls7504gxl4re9fag0",
"amount": "0.0005"
}
],
"feeOptions": {
"priority": "standard",
"exactAmount": "0.00001"
},
"prepareStrategy": "minimize-dust",
"replaceable": false
}
}
}
{
"apiVersion": "2024-12-12",
"requestId": "601c1710034ed6d407996b30",
"context": "yourExampleString",
"data": {
"item": {
"fee": {
"amount": "0.0000035",
"unit": "BTC"
},
"feePerByte": {
"amount": "0.00000001",
"unit": "BTC"
},
"size": 314,
"version": 2,
"locktime": 0,
"additionalData": "yourAdditionalDataHere",
"inputs": [
{
"address": "tb1q7cer5fh3w656jpe30gudzjg05j0kmd48jwxhzh",
"outputIndex": 1,
"satoshis": 76772,
"script": "0014f6323a26f176a9a907317a38d1490fa49f6db6a7",
"sighash": "737a05f70bb0ff41adb2328585374804675da49d19d72a346569a01c180083db",
"transactionId": "8347b87d6956dc5c0bccf7f40227c7570d1bd66480fc38e660079a18c3bc21e1"
}
],
"outputs": [
{
"address": "tb1qsf7w5q7pnrumkm6r9zct4ls7504gxl4re9fag0",
"satoshis": 50000,
"script": "0014827cea03c198f9bb6f4328b0bafe1ea3ea837ea3"
}
]
}
}
}