# submit-snipe

This endpoint accepts a pair of competing transactions and submits the first to the Jito block engine while sending the second through bloXroute staked connections. Both transactions must include a minimum bloXroute tip of `0.001` SOL, and the first transaction must also include a valid tip to one of Jito’s tipping [wallets](https://jito-foundation.gitbook.io/mev/mev-payment-and-distribution/on-chain-addresses).

Since the first transaction is submitted through Jito-protected flow, a priority fee is generally not required, while the second transaction sent through staked connections should include a competitive priority fee.

{% hint style="info" %}
If you do not want both sniping transactions to land successfully, you are responsible for making them mutually exclusive, such as by using the same durable nonce so that the first landing transaction invalidates the other.
{% endhint %}

## Request <a href="#request" id="request"></a>

**Method:**

`POST ./api/v2/submit-snipe`

**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:

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

```bash
curl -X 'POST' \
  'http://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
}'
```

{% endtab %}
{% endtabs %}

## **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**:

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

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

{% 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-snipe.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.