Submit Signed Transaction

This endpoint is used to submit signed singular transaction.

Transactions submitted to this endpoint must include a bloXroute memo instruction in order to be processed. If you are using the Trader API endpoints or SDKs the instruction will be added automatically. If you want to construct your own transaction and use our submit endpoint, please read more about Transaction Submission. Elite & Ultra tier customers will be exempted if the transaction submitted includes a tipping instruction, to save an instruction in the transaction.

Request

Method:

POST ./api/v2/submit

Parameters:

Parameter	type	Description
transaction	TransactionMessage	See TransactionMesssage below
skipPreFlight	boolean	OPTIONAL. Useful for disabling transaction simulation before actual submission. true or false, Default False
frontRunningProtection	boolean	OPTIONAL. Specify if you would like to enable the Front-Running Protection feature. The transaction must include an Tip instruction to pay for the service fee. You can include an Tip instruction but set this field to False. In this case, Trader API will propagate to both Jito and publicly. Default False.
fastBestEffort	boolean	OPTIONAL. This is an optional parameter that effects the behavior of frontRunningProtection which must be set to True to use this feature. Enabling this parameter will allow you to submit your transaction not only to the Jito but also to bloXroute-identified low-risk validators.
useStakedRPCs	boolean	OPTIONAL. An tip instruction with a minimum of 0.001 SOL is required and frontRunningProtection must be set to False to use this feature. When enabled, Trader API will use weighted stake qOS to submit your transaction to the Leader. The cost will be 10% of the tip amount.
allowBackRun	boolean	OPTIONAL. Specify if you would like to enable OFA(Order Flow Auction) submission option. Transaction will be sent to OFA MEV searcher. If there was any MEV profit, you will receive part of the MEV profit back as a rebate.
revenueAddress	string	OPTIONAL. Specify this field ONLY when you enable the allowBackRun parameter. The MEV rebate will be send to the specified address.

TransactionMessage

Parameter	type	Description
content	txbase64Payload	Raw bytes of signed transaction.

Request example:

HTTP

curl -X 'POST' \
  'https://ny.solana.dex.blxrbdn.com/api/v2/submit' \
  -header "Authorization: $AUTH_HEADER" \
  -d '{
    "transaction": {"content": "AjF+...CQ=="}, 
    "frontRunningProtection": False,
    "useStakedRPCs": False,
    "allowBackRun": True,
    "revenueAddress": "6d...FY"
}'

WebSocket

wscat -c wss://ny.solana.dex.blxrbdn.com/ws --execute '{"jsonrpc": "2.0", "id": 1, "method": "PostSubmit", "params": {
  "transaction": {"content": "AjF+Br...Q=="}
}}'

Python

# submitting raw transactions
await api.post_submit("AjF+B...Q==")

TypeScript

await provider.postSubmit({
    transaction: { content: encodedTxn, isCleanup: false },
    skipPreFlight: true,
})

Response:

Fields:

Parameter	Type	Description
signature	string	Solana signature of the submitted transaction

Example:

JSON

{
  "signature":"zPiAEU8...ak3Fq"
}

You can look up this signature in a Solana Explorer like SolScan or Solana Explorer.