Skip to main content

POST /bundle

Simple REST endpoint for submitting a Jito-compatible bundle. Alternative to the JSON-RPC sendBundle method — same logic, simpler request format. If your bundle does not include a Jito tip transaction, the relay automatically sponsors one and appends it.

Servers

RegionEndpoint
Frankfurthttps://fra.send.raze.sh/bundle
Amsterdamhttps://ams.send.raze.sh/bundle
Chicagohttps://chi.send.raze.sh/bundle
Singaporehttps://sg.send.raze.sh/bundle

Request

POST /bundle
Content-Type: application/json

{
  "transactions": [
    "<encoded_tx_1>",
    "<encoded_tx_2>"
  ],
  "encoding": "base58"
}
FieldTypeRequiredDefaultDescription
transactionsstring[]YesArray of signed transactions (1–5)
encodingstringNo"base58""base58" (Jito-compatible) or "base64"

Bundle constraints

  • Max 5 transactions if your bundle already includes a Jito tip
  • Max 4 transactions if no Jito tip — relay appends its own tip as the 5th
  • At least 1 transaction required

Response

Success:
{
  "success": true,
  "bundle_id": "4xTWpZFcQh8mK3nRJjz3wXBoRgixCa6xjnB7YaB1pPB263..."
}
Error:
{
  "success": false,
  "error": "bundle must contain at least 1 transaction"
}
HTTP StatusMeaning
200Bundle submitted (check success field — Jito may still reject)
400Invalid request (decode failure, too many txs, empty bundle)
502Jito Block Engine unreachable
503Bundle sending not configured or blockhash not ready

Code examples

curl -X POST https://fra.send.raze.sh/bundle \
  -H "Content-Type: application/json" \
  -d '{
    "transactions": ["<base58_tx_1>", "<base58_tx_2>"],
    "encoding": "base58"
  }'