submit-batch

This endpoint allows you to submit multiple signed transactions under a single request to reduce network call overhead. Additionally supports block engine bundles.

Enabling useBundle=true may introduce additional latency because transactions are routed through bundle engines across multiple hops. Use it only when revert protection is required or execution speed is not critical.

The maximum batch size is 25 signed transactions. If useBundle=true, the maximum batch size is reduced to 4 signed transactions to adhere to third-party block engine requirements.

Each signed transaction in the batch must satisfy the standard tip requirements described in our tip documentation here. When useBundle=true, the tip should only be included in the final transaction in the batch.

Request

Method:

POST ./api/v2/submit-batch

Parameters:

Parameter	Type	Description
entries	PostSubmitRequestEntry []	A list of signed transactions. See PostSubmitRequestEntry below
useBundle	boolean	OPTIONAL. Specify if you would like to send transactions as a bundle only (all transactions land or none at all). 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.

PostSubmitRequestEntry

Parameter		Description
transaction	TransactionMessage	See TransactionMessage below
skipPreFlight	boolean	OPTIONAL. Useful for disabling transaction simulation before actual submission. Default false.

TransactionMessage

Parameter		Description
content	txbase64Payload	Base64 signed transaction bytes

Request example:

HTTP

curl -X POST "http://ny.solana.dex.blxrbdn.com/api/v2/submit-batch" \
  -H "Authorization: $AUTH_HEADER" \
  -H "Content-Type: application/json" \
  -d '{
    "entries": [
      {
        "transaction": {
          "content": "AayHbuFlHrJV5V53CAyBW0IM6PHeqfbIF2PegMEU..."
        },
        "skipPreFlight": false
      },
      {
        "transaction": {
          "content": "AeNTbB0vnGNSGVybg/mzbtfZzmwvNPJsWgmQJshxK..."
        },
        "skipPreFlight": false
      },
      {
        "transaction": {
          "content": "AUTTE4Oa9qKhimePjDHGpnh9F5FtRfMwuPuVGyxytt..."
        },
        "skipPreFlight": false
      }
    ],
    "useBundle": false,
    "frontRunningProtection": false
  }'

WebSocket

Response:

Fields:

Field	Type	Description
transactions	list	A list of signatures.

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

Example:

JSON

{
	"transactions": [
		{
			"signature": "4T4ou8LBZ3y8mDvJQyv6FwzWYyrVun6imocEJPTsZ8sqM6BwzhjErujAyj3xMD1SDjysxVP2pAopKR8yHkCGUhon",
			"submitted": true
		},
		{
			"signature": "5YcHd1LwkzfPACWBdBq7rfb1pRMf9ypyp4tJrngMpN8nTJnG11NGLA8KMaoUrWivWtVRyCcjXP9oaGmJSsJhpGBk",
			"submitted": true
		},
		{
			"signature": "2NowWRYoqFibBrz7b8iivtyhoc6WRx1WSN9ZusbEcXk4Waw5a1udYkBbK7x5eYVfLyQsN116ND1VmVoeHUgyNh7b",
			"submitted": true
		}
	]
}

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