Boost Transaction
Overview
Functionality: Boost and broadcast transactions
API Key authentication: Access to all endpoints requires the
x-api-keyheader provided by SaturnAddress parameter: All requests must have the
Content-Typeheader ofapplication/jsonand provide theaddressin the body of the wallet that is requesting the broadcast.
Endpoints
Boost an array of transaction ids. User must own some of the outputs of those transactions. The response will contain a PSBT that can be signed by the user. You can then broadcast the PSBT using the /broadcast endpoint.
The rune address of the user. It must be a taproot address. (P2TR). If no bitcoin address is provided, the rune address will be used for bitcoin too.
The bitcoin address of the user.
The rune public key of the user.
^[0-9a-fA-F]+$The payment public key of the user.
^[0-9a-fA-F]+$The transaction ids to boost.
POST /v0/transaction/boost HTTP/1.1
Host: api-dev.saturnbtc.io
x-api-key: YOUR_API_KEY
Content-Type: application/json
Accept: */*
Content-Length: 121
{
"runeAddress": "text",
"paymentAddress": "text",
"runePublicKey": "text",
"paymentPublicKey": "text",
"transactionIds": [
"text"
]
}{
"psbt": "text",
"fee": "text",
"newFeeRate": 1,
"feeRate": 1,
"utxosToSign": [
{
"address": "text",
"signingIndexes": [
1
],
"sigHash": 1,
"utxo": "text"
}
]
}Broadcast a signed transaction.
The rune address of the user. It must be a taproot address. (P2TR). If no bitcoin address is provided, the rune address will be used for bitcoin too.
The bitcoin address of the user.
The signed PSBT of the transaction.
The type of the transaction.
POST /v0/transaction/broadcast HTTP/1.1
Host: api-dev.saturnbtc.io
x-api-key: YOUR_API_KEY
Content-Type: application/json
Accept: */*
Content-Length: 80
{
"runeAddress": "text",
"paymentAddress": "text",
"signedPsbt": "text",
"txType": null
}textLast updated