POST /bundle
Simple REST endpoint for submitting a Jito-compatible bundle. Alternative to the JSON-RPCsendBundle 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
| Region | Endpoint |
|---|---|
| Frankfurt | https://fra.send.raze.sh/bundle |
| Amsterdam | https://ams.send.raze.sh/bundle |
| Chicago | https://chi.send.raze.sh/bundle |
| Singapore | https://sg.send.raze.sh/bundle |
Request
| Field | Type | Required | Default | Description |
|---|---|---|---|---|
transactions | string[] | Yes | — | Array of signed transactions (1–5) |
encoding | string | No | "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:| HTTP Status | Meaning |
|---|---|
200 | Bundle submitted (check success field — Jito may still reject) |
400 | Invalid request (decode failure, too many txs, empty bundle) |
502 | Jito Block Engine unreachable |
503 | Bundle sending not configured or blockhash not ready |
Code examples
- curl
- Node.js
- Python
- Rust
