Submit a Transaction
Use this endpoint to send a single transaction faster than the p2p network using the BDN.
Last updated
Use this endpoint to send a single transaction faster than the p2p network using the BDN.
Last updated
Method: blxr_tx
transaction
Raw transactions bytes without 0x
prefix.
blockchain_network
Blockchain network name.
Optional. Default: Mainnet
Available options are: Mainnet
for ETH Mainnet, BSC-Mainnet
for BSC Mainnet
*Use with Cloud-API when working with BSC.
node_validation
Transaction is sent to the blockchain node for validation, and the Gateway returns any error message received in response.
Available only with Gateway API
Optional
Default: False
The WebSocket endpoint for sending transactions is wss://api.blxrbdn.com/ws
. All users sending transactions via a WebSocket connection should use this endpoint.
See to work directly with IP ( wss://<IP>/ws
)
The HTTPS POST endpoint is https://api.blxrbdn.com
.
Examples
Gateway WebSocket endpoint: ws://127.0.0.1:28333/ws
We assume the WebSocket port 28333
.
tx_hash
Transaction hash
The bloXroute best practice is for users to send transactions to both the Gateway-API and to their blockchain node. You should send transactions in parallel to the Gateway and to your blockchain node as a backup.
Users should not send transactions to the transactions streams WebSocket endpoint
wss://<REGION>.<NETWORK>.blxrbdn.com/ws
(e.g.wss://virginia.eth.blxrbdn.com/ws
) which is for streaming only and doesn't support sending transactions.
Mandatory. Learn more about constructing the transaction .
Please check to reconstruct the header.
Sending Transactions to the Cloud-API or Gateway-API requires you to register an account on the . During the registration process, a certificate, private key, and secret hash will be generated for your account. The certificate and key will be used to authenticate your account.