submit-snipe

This endpoint is designed to maximize your landing speed for a pair of transactions that compete with each other (mainly token sniping use case).

The requirements for such transactions are to have a minimum Jito tip (we support only direct transfer instruction) of 0.001SOL and a minimum bloXroute tip of 0.0001 SOL. The higher the bloXroute tip is the higher the chance to land it in an aggregated bundle.

This endpoint receives a pair of transactions and sends one to the Jito engine and the second to swQoS or white-listed leaders (the same set used for fastBestEffort)

• Call this endpoint with an array of two transactions

• In case you don’t want two sniping transactions to be landed successfully at once, you are responsible for reverting one of these transactions when the other lands first.

• The first transaction will be sent to Jito and has the same requirements as described above. Since it will be sent just to Jito, there is no need for a Priority Fee. Both Jito and bloXroute tips are required

• The second transaction will be sent to bloXroute routing infra either using swQOS or fastBestEffort. A priority fee and bloXroute tip are required. The useStakedRPCs parameter is optional and can be used when submitting the 2nd transaction. If not provided or if False, fastBestEffort is used.

Request

Method:

POST ./api/v2/submit-snipeComment

Parameters:

Parameter	Type	Description
entries	PostSubmitRequestEntry []	A list of signed transaction. See PostSubmitRequestEntry below
useStakedRPCs	boolean	OPTIONAL. Specify if you would like to send transactions using staked RPCs. If not provided or if False, fastBestEffort is used. Default False.

PostSubmitRequestEntry

Parameter	Text	Description
transaction	TransactionMessage	See TransactionMessage below

TransactionMessage

Parameter	Text	Description
content	txbase64Payload	Raw bytes of signed transaction.

Request example:

HTTP

curl -X 'POST' \
  'https://ny.solana.dex.blxrbdn.com/api/v2/submit-snipe' \
  -header "Authorization: $AUTH_HEADER" \
  -d '{
 "entries": [{transaction": {"content": "AjF+...AAABCQ=="}}, {transaction": {"content": "Bdej+...AdsaCQ=="}}],
 "useStakedRPCs": true
}'

Response:

Fields:

Field	Type	Description
transactions	list	A list of signature.

Field	Type	Description
signature	string	Solana signature of the submitted transaction
error	string	Return error message.
submitted	boolem	If the transaction has been submitted.

Example:

JSON

{
    "transactions": [
        {
            "signature": "AvuWl0d...AABoEA", 
            "submitted": true
        }, 
        {
            "signature": "AVfRxLb...gYnkgY", 
            "submitted": true
        }
    ]
}

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