> For the complete documentation index, see [llms.txt](https://docs.blockrazor.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.blockrazor.io/transaction-submission/transaction-sending/solana/send-bundle.md).

# Solana Send Bundle API Reference

Use the BlockRazor Solana Send Bundle API. Review the endpoint, parameters, and request example.

{% hint style="warning" %}
Solana's bundle sending service is not bound to the subscription plan and is not available by default. If you need to increase the BPS limit, please [contact](https://discord.com/invite/qqJuwRb8Nh) us and we will handle it as soon as possible.
{% endhint %}

`Send Bundle` is a bundle sending interface provided by BlockRazor for Solana, used to send signed transactions to the blockchain in bundle form with low latency.

A maximum of four transactions can be sent in a single bundle. These transactions are executed sequentially, and if any one transaction fails, the entire bundle will fail.

To enhance MEV protection, use any valid Solana public key starting with `jitodontfront` and `dontbund1e` in the instructions of the first transaction in the bundle. If the transaction is subjected to a frontrun attack, it will be rejected by the Jito/Harmonic block engine.

### Endpoint <a href="#xian-liu" id="xian-liu"></a>

* `POST /sendBundle`
* `gRPC`

### Transaction Construction Example <a href="#jiao-yi-gou-jian-dai-ma-shi-li" id="jiao-yi-gou-jian-dai-ma-shi-li"></a>

* [Curl](/transaction-submission/transaction-sending/solana/send-bundle/curl.md)
* [Go](/transaction-submission/transaction-sending/solana/send-bundle/go.md)
* [Rust](/transaction-submission/transaction-sending/solana/send-bundle/rust.md)
* [JS](/transaction-submission/transaction-sending/solana/send-bundle/js.md)

### Request Parameter

<table><thead><tr><th width="111.44921875">Parameters</th><th width="115.421875">Mandatory</th><th width="104.94140625">Format</th><th width="109.98046875">Example</th><th>Description</th></tr></thead><tbody><tr><td>transactions</td><td>Mandatory</td><td>string[]</td><td>["$base64_tx_1","$base64_tx_2","$base64_tx_3"]</td><td>Fully signed transactions, Base64 encoding protocal </td></tr><tr><td>mode</td><td>Optional</td><td>string</td><td>"sandwichMitigation"</td><td>If "sandwichMitigation" is provided, the bundle protection mode will be enabled; otherwise, it will not be enabled.</td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.blockrazor.io/transaction-submission/transaction-sending/solana/send-bundle.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
