submit

This endpoint is used to submit signed singular transaction.

Customers with a Free Tier subscription (or higher) are able to submit transactions through the Solana Trader API.

Learn more about all the regions you can submit transactions to by checking the Regions page.

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. Our infrastructure scores current and upcoming slot leaders in real time, identifying validators with an elevated risk of malicious ordering. High-risk leaders (identified through sandwich correlations and validator behaviour analytics) are delayed or skipped. Low-risk leaders receive accelerated submission through staked connections, improving both protection and time-to-land. Default False.
revertProtection	boolean	OPTIONAL. Enable revertProtection=true to prevent failed transactions from landing on-chain — useful for atomic or conditional strategies, though it introduces latency.
submitProtection	enum	OPTIONAL. Specifies the desired level of MEV protection for the transaction. Accepted Values:SP_LOW, SP_MEDIUM (default), and SP_HIGH Behaviour by Level: SP_LOW: No MEV protection is applied. Transactions are submitted directly to Jito without delay, even if a known malicious validator is active. Ideal for transactions that are not vulnerable to sandwich attacks, but still benefit from Jito’s revert protection. SP_MEDIUM: Provides moderate protection. If the current slot is at least three slots away from any known malicious validator, the transaction is submitted immediately. If a malicious validator is the current leader or will become the leader in fewer than 3 slots, the system waits until four consecutive safe slots are observed before submitting. SP_HIGH: Provides maximum protection. Transactions are delayed until eight consecutive safe slots have passed, ensuring the highest level of avoidance from malicious 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.
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

# USE HTTP, NOT HTTPS, FOR THE BEST PERFORMANCE
# THE FOLLOWING IS THE CONFIGURATION FOR FASTEST PROPAGATION

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

WebSocket

Python

TypeScript

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.