# submit

{% hint style="info" %}
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](/solana/trader-api/introduction/regions.md) page. 
{% endhint %}

## Request

#### Method: 

`POST ./api/v2/submit`

#### Parameters:

<table><thead><tr><th width="190">Parameter</th><th width="216.2">type</th><th width="449">Description</th></tr></thead><tbody><tr><td><code>transaction</code></td><td><code>TransactionMessage</code></td><td>See <code>TransactionMesssage</code> below</td></tr><tr><td><code>skipPreFlight</code></td><td>boolean</td><td><strong>OPTIONAL.</strong> Useful for disabling transaction simulation before actual submission. <code>true</code> or <code>false</code>, Default <code>False</code></td></tr><tr><td><code>frontRunningProtection</code></td><td>boolean</td><td><strong>OPTIONAL.</strong> 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 <code>False</code>.</td></tr><tr><td><code>revertProtection</code></td><td>boolean</td><td><strong>OPTIONAL.</strong> Enable revertProtection=true to prevent failed transactions from landing on-chain — useful for atomic or conditional strategies, though it introduces latency.</td></tr><tr><td><code>submitProtection</code></td><td>enum</td><td><p><strong>OPTIONAL.</strong> Specifies the desired level of MEV protection for the transaction. <strong>Accepted Values:</strong><code>SP_LOW</code>, <code>SP_MEDIUM</code> (default), and <code>SP_HIGH</code></p><p><strong>Behaviour by Level:</strong></p><ul><li><strong><code>SP_LOW</code></strong>: No MEV protection is applied. Transactions are submitted directly to Jito without delay, even if a known malicious validator is active.
<br>Ideal for transactions that are not vulnerable to sandwich attacks, but still benefit from Jito’s revert protection.</li><li><p><strong><code>SP_MEDIUM</code></strong>: Provides moderate protection.</p><ul><li>If the current slot is at least three slots away from any known malicious validator, the transaction is submitted immediately.</li><li>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.</li></ul></li><li><p><strong><code>SP_HIGH</code></strong>: Provides maximum protection.</p><ul><li>Transactions are delayed until eight consecutive safe slots have passed, ensuring the highest level of avoidance from malicious validators.</li></ul></li></ul></td></tr><tr><td><code>useStakedRPCs</code></td><td>boolean</td><td><strong>OPTIONAL.</strong> An <strong><code>tip</code></strong> instruction with a minimum of 0.001 SOL is required and <code>frontRunningProtection</code> 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. </td></tr><tr><td><code>allowBackRun</code></td><td>boolean</td><td><strong>OPTIONAL.</strong> 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. </td></tr><tr><td><code>revenueAddress</code></td><td>string</td><td><strong>OPTIONAL.</strong> Specify this field ONLY when you enable the <code>allowBackRun</code> parameter. The MEV rebate will be send to the specified address. </td></tr></tbody></table>

`TransactionMessage`

<table><thead><tr><th width="236">Parameter</th><th width="194.2">type</th><th width="369">Description</th></tr></thead><tbody><tr><td><code>content</code></td><td>txbase64Payload</td><td>Raw bytes of signed transaction.</td></tr></tbody></table>

#### Request example:

{% tabs %}
{% tab title="HTTP" %}

<pre class="language-bash"><code class="lang-bash"><strong># USE HTTP, NOT HTTPS, FOR THE BEST PERFORMANCE
</strong># THE FOLLOWING IS THE CONFIGURATION FOR FASTEST PROPAGATION

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

{% endtab %}

{% tab title="WebSocket" %}

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

{% endtab %}

{% tab title="Python" %}

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

{% endtab %}

{% tab title="TypeScript" %}

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

{% endtab %}
{% endtabs %}

### Response:

#### Fields:

<table><thead><tr><th width="214">Parameter</th><th width="110">Type</th><th width="422">Description</th></tr></thead><tbody><tr><td><code>signature</code></td><td>string</td><td>Solana signature of the submitted transaction</td></tr></tbody></table>

#### Example:

{% tabs %}
{% tab title="JSON" %}

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

{% endtab %}
{% endtabs %}

You can look up this signature in a Solana Explorer like [SolScan](https://solscan.io/) or [Solana Explorer](https://explorer.solana.com/).


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.bloxroute.com/solana/trader-api/api-endpoints/transaction-submisson/submit.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.