sendrawtransaction

sendrawtransaction submits a fully signed Bitcoin transaction, given as serialized hex, to the node's mempool and relays it across the Bitcoin peer-to-peer network. On success it returns the transaction's txid, which you can then track until it is mined into a block — roughly every ten minutes under Bitcoin's Proof-of-Work. This is the broadcast step that actually moves BTC after a transaction has been built and signed. Send the request to the Bitcoin JSON-RPC endpoint at https://bitcoin.therpc.io/YOUR_API_KEY.

Use cases

• Broadcast a transaction that was signed offline or on a hardware wallet, keeping the signing keys away from the endpoint entirely.
• Submit a transaction assembled with createrawtransaction once it has been funded, signed, and verified.
• Push a fee-bumped RBF replacement that spends the same inputs at a higher fee to get a stuck transaction confirmed.

Parameters

Response

Example request

1curl https://bitcoin.therpc.io/YOUR_API_KEY \
2  -X POST \
3  -H "Content-Type: application/json" \
4  -d '{
5  "jsonrpc": "1.0",
6  "id": "therpc",
7  "method": "sendrawtransaction",
8  "params": [
9    "0200000001abcd...00000000"
10  ]
11}'

Errors & troubleshooting

Common pitfalls

• The hex must be a fully signed transaction; this method never signs for you, and an unsigned or partially signed tx is rejected with a decode or policy error.
• The default maxfeerate of 0.10 BTC/kvB is a guardrail that rejects accidentally over-fee transactions. Pass 0 only when you deliberately intend to send a very high fee rate.
• Broadcasting from a single endpoint can reveal which node originated the transaction. The txid is returned only when the node accepts the tx; a rejection (error -26) means it never entered the mempool.

Supported networks

• Mainnet
• Testnet

See also

• testmempoolaccept
• createrawtransaction
• getrawtransaction