Boost Transaction

Overview

Functionality: Boost and broadcast transactions
API Key authentication: Access to all endpoints requires the x-api-key header provided by Saturn
Address parameter: All requests must have the Content-Type header of application/json and provide the address in the body of the wallet that is requesting the broadcast.

Endpoints

Last updated 3 months ago

Boost an array of transaction ids. User must own some of the outputs of those transactions

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.

post

/v0/transaction/boost

Authorizations

Body

runeAddressThe rune address of the user. It must be a taproot address. (P2TR)required

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.

paymentAddressThe bitcoin address of the user

The bitcoin address of the user.

runePublicKeyThe rune public key of the userrequired

The rune public key of the user.

Pattern: ^[0-9a-fA-F]+$

paymentPublicKeyThe payment public key of the user

The payment public key of the user.

Pattern: ^[0-9a-fA-F]+$

transactionIdsThe transaction ids to boostrequired

The transaction ids to boost.

Responses

application/json

cURL

JavaScript

Python

HTTP

curl -L \
  --request POST \
  --url 'https://api-dev.saturnbtc.io/v0/transaction/boost' \
  --header 'x-api-key: YOUR_API_KEY' \
  --header 'Content-Type: application/json' \
  --data '{"runeAddress":"text","runePublicKey":"text","transactionIds":[null]}'

201

400

401

403

{
  "psbt": "text",
  "fee": "text",
  "newFeeRate": 1,
  "feeRate": 1,
  "utxosToSign": [
    {
      "address": "text",
      "sigHash": 1,
      "utxo": "text",
      "signingIndexes": [
        1
      ]
    }
  ]
}

Broadcast a signed transaction

Broadcast a signed transaction.