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.Documentation Index
Fetch the complete documentation index at: https://helius-auto-translations.mintlify.app/llms.txt
Use this file to discover all available pages before exploring further.
Endpoint
Request
"2.0"Request identifier.
"sendBundle"Array of up to 5 fully-signed transactions, base64 encoded.
"base64" (recommended) or "base58". Default: "base58".Headers
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
Bundle ID (SHA-256 hash of the transaction signatures). Use with
getBundleStatuses to track landing.See Also
- Jito Bundles via Helius — full guide with region routing, tip accounts, and requirements
- getBundleStatuses — check bundle landing status
- simulateBundle — test bundles before submitting