Loading documentation…
Submit a signed Solana transaction over rpc edge, through the low-latency sender path where enabled.
sendTransaction submits a fully signed, serialized transaction to the network. On rpc edge, where
transaction sender access is enabled, submissions take the low-latency path
to the current and upcoming leaders rather than a generic forward.
A successful response returns the transaction signature - it means the transaction was accepted for processing, not that it landed. Confirm landing with getSignatureStatuses or by watching the signature.
The transaction must already be signed and base64-encoded.
curl -s https://rpc.rpcedge.com \
-H 'content-type: application/json' \
-H 'x-api-key: YOUR_UUID_KEY' \
-d '{
"jsonrpc": "2.0",
"id": 1,
"method": "sendTransaction",
"params": ["<base64-encoded-signed-tx>", { "encoding": "base64", "skipPreflight": false, "maxRetries": 5 }]
}'| Position | Name | Type | Notes |
|---|---|---|---|
0 | transaction | string | Signed, serialized transaction. |
1 | config | object | Optional. Fields below. |
| Field | Type | Notes |
|---|---|---|
encoding | string | base64 (recommended) or base58. |
skipPreflight | bool | Skip the preflight simulation. Faster, but you lose the pre-send error check. |
preflightCommitment | string | Commitment for the preflight sim. Defaults to finalized. |
maxRetries | number | How many times the node rebroadcasts before giving up. |
minContextSlot | number | Fail if the node is behind this slot. |
{ "jsonrpc": "2.0", "id": 1, "result": "5VERv8...signature...9nT" }result is the base-58 transaction signature. On a preflight failure the call returns a JSON-RPC
error instead - inspect error.data.logs for the on-chain reason (see errors).