Submit a signed transaction (or Jito bundle)

Submits one signed VersionedTransaction to the network, OR — when bundle: true — submits 1–5 signed transactions atomically as a Jito bundle. Replaces /v1/tx/submit and /v1/tx/submit-jito. Emits transaction.submitted.

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Body Params
string

base64-encoded signed VersionedTransaction. Required when bundle is false/omitted.

signed_transactions
array of strings
length between 1 and 5

1–5 base64-encoded signed VersionedTransactions to submit as a single Jito bundle. Required when bundle is true.

signed_transactions
boolean
Defaults to false

If true, treat the request as a Jito bundle submission and require signed_transactions. If false/omitted, treat as a standard single-tx submit and require transaction.

boolean
Defaults to false
integer
0 to 10
Defaults to 2
tracked_resource
object

Optional. Tell the tx-watcher which resource this transaction relates to. On confirmed it will additionally emit each related_events (e.g. pool.live, stake.acquired).

string
length between 1 and 128
^[A-Za-z0-9_\-.:]+$

Optional client-supplied identifier echoed on the response. Prefer metadata for richer reconciliation.

metadata
object

Free-form string key/value bag echoed back on responses and webhook events.

Headers
string
length between 1 and 128

Optional client-supplied request ID, echoed in X-Request-Id response header.

string
length between 1 and 255

Client-supplied key (UUID v4 recommended) for safe write retries. Server stores (key, request_hash, response) and replays. Reusing with a different body returns 409 idempotency_conflict.

Responses

Language
Credentials
Bearer
URL
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json