Skip to main content
Submit a bundle of up to 5 fully-signed transactions for atomic execution. All transactions execute sequentially — if any fails, the entire bundle is rejected. Requires a tip to a Jito tip account in at least one transaction.

Rate Limits

sendBundle is rate limited to 5 requests per second per project. getBundleStatuses and simulateBundle use the general RPC rate limit.
Need higher rate limits? Contact our sales team.

Endpoint

Request

string
required
"2.0"
number
required
Request identifier.
string
required
"sendBundle"
array[string]
required
Array of up to 5 fully-signed transactions, base64 encoded.
string
"base64" (recommended) or "base58". Default: "base58".

Query Parameters

boolean
default:"false"
When true, routes your bundle away from validators statistically linked to sandwich attacks. Opt-in per request. See MEV Protect.

Headers

string
Optional. Route to a specific Jito Block Engine region. Values: ams, dub, fra, lon, nyc, slc, sgp, tyo, mainnet. If omitted, routes to the global endpoint (geo-routed to nearest).

Request Example

Response

string
Bundle ID (SHA-256 hash of the transaction signatures). Use with getBundleStatuses to track landing.

See Also