Public Transactions
The blxr_tx endpoint allows users to send a single transaction faster than the p2p network using the BDN. The endpoint returns a transaction hash.
This service is available via both the Cloud API and Gateway API.
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.
For latency-sensitive orderflow, WebSocket is recommended and can provide latency improvement over HTTP/HTTPS. If you prefer to short-lived connections, use HTTP over HTTPS for improved latency.
Submission Endpoint
Method:
blxr_txCloud API Endpoint:
api.blxrbdn.comGateway API Endpoint:
127.0.0.1:28333/ws(assumes WebSocket port 28333)Request type:
HTTPS,WSS
Parameters
transaction
Raw transactions bytes without 0x prefix.
Mandatory. Learn more about constructing the transaction here.
blockchain_network
Blockchain network name.
Mandatory. Use 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
Example
Cloud-API
Gateway-API:
Response
Last updated