Boost Transaction
Overview
Functionality: Boost and broadcast transactions
API Key authentication: Access to all endpoints requires the
x-api-key
header provided by SaturnAddress parameter: All requests must have the
Content-Type
header ofapplication/json
and provide theaddress
in 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
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 address of the user. If no secondary address is provided, the primary address must be a taproot address. (P2TR)
The secondary address of the user. Must be a taproot address. (P2TR)
The public key of the user.
The secondary public key of the user.
The transaction ids to boost.
The PSBT of the boosted transaction.
The fee of the boosted transaction.
The new fee rate of the boosted transaction.
The fee rate of the boosted transaction.
The inputs to sign for the boosted transaction.
Broadcast a signed transaction
Broadcast a signed transaction.
The address of the user. If no secondary address is provided, the primary address must be a taproot address. (P2TR)
The secondary address of the user. Must be a taproot address. (P2TR)
The signed PSBT of the transaction.
The type of the transaction.
Last updated