Jito Block Engine sendBundle (with landing confirmation)
RPC
Jito Block Engine sendBundle (with landing confirmation)
JSON-RPC 2.0 endpoint that submits a bundle to the Jito Block Engine and waits for it to land.
Internally calls sendJitoBundle, which simulates the bundle, sends it to
https://<region>.mainnet.block-engine.jito.wtf/api/v1/bundles, polls signature status until the
first transaction is confirmed (up to ~30s), and retries on failure.
Spec reference: https://docs.jito.wtf/lowlatencytxnsend/#sendbundle
Notes:
- On success the response is HTTP 200 with a
resultobject. On failure the response is HTTP 400 with a JSON-RPCerrorenvelope. - Bundle size is capped at 5 transactions (Jito limit).
- Transactions must already include a tip instruction; this endpoint does NOT inject tips.
- Transactions must be fully signed (all required signatures present) before submission. Unsigned bundles return HTTP 400 with JSON-RPC INVALID_PARAMS and
data.unsignedIndiceslisting the offending positions. - This endpoint blocks until the bundle lands or polling/retries are exhausted.
POST
Jito Block Engine sendBundle (with landing confirmation)
Documentation Index
Fetch the complete documentation index at: https://docs.lpagent.io/llms.txt
Use this file to discover all available pages before exploring further.
Authorizations
API key for authentication
Query Parameters
Jito block engine region
Available options:
mainnet, amsterdam, frankfurt, ny, tokyo Body
application/json
Available options:
2.0 Available options:
sendBundle [transactions[] (1-5 base58/base64 encoded txs), options? ({ encoding: 'base58' | 'base64' })]
Required array length:
1 - 2 elementsRequest id, echoed back in the response