sendTx
POST /sendtx submits a serialized Solana transaction over plain HTTP to Triton's Jet sending engine, without JSON-RPC.
/sendtx is available on Triton's Solana mainnet endpoints. Devnet and testnet support depends on the pool, so check with Triton before relying on it there.
Why use it over sendTransaction
A sendTransaction call wraps your transaction in a JSON-RPC envelope, which adds overhead at every stage. /sendtx strips that away:
No JSON parsing. The server reads your transaction bytes directly, with no JSON deserialisation.
Fewer CORS preflights. A
text/plainbody (base58, or base64 withencoding=base64) is a CORS-safelisted request, so browsers skip the preflightOPTIONSround-trip. Raw bytes (application/octet-stream) and theSolana-ForwardingPoliciesheader each make the browser send a preflight first.Smaller payloads. Without the
jsonrpc,id,method, andparamswrapper, the request body is smaller on the wire.Simpler clients. A single HTTP
POST, with no Solana JSON-RPC client library.
This suits browser apps that are sensitive to preflight latency and high-frequency backends sending large volumes. If you need full sendTransaction options such as skipPreflight, keep using sendTransaction.
Request
Method
POST
Path
/sendtx
Send the serialized transaction as the request body, one of two ways:
Raw bytes. Set
Content-Type: application/octet-streamand send the transaction as a binary payload.Encoded string. Set
Content-Type: text/plainand send the transaction as base58 or base64 text, with theencodingparameter set to match. AnyContent-Typeother thanapplication/octet-stream, or none, is read as text.
Query parameters
encoding
base58, base64
No
Encoding of a text-body transaction. Defaults to base58. Not allowed with Content-Type: application/octet-stream.
response
signature, none
Recommended
signature returns the transaction signature in the response body on success. none, the default, returns an empty body.
max_retries
integer
No
Accepted for compatibility, but it has no effect: Triton doesn't retry or rebroadcast on the server. Rebroadcast from your client until the transaction confirms or its blockhash expires.
Optional headers
Solana-ForwardingPolicies
Comma-separated Yellowstone Shield policy addresses (policy PDAs) to apply when forwarding. Entries that aren't valid addresses are ignored. This header is read only on /sendtx; with sendTransaction, use the forwardingPolicies parameter.
Examples
Response
On success, the endpoint returns HTTP 200. If response=signature was set, the body is the transaction signature as plain text. Otherwise the body is empty, and you derive the signature client-side from the signed transaction before submitting, since it is deterministic.
An invalid request returns HTTP 400 with a plain-text error message: for example, an unsupported encoding or response value, encoding sent with application/octet-stream, an empty body, or a body that doesn't decode to a valid transaction. Methods other than POST return HTTP 405, except the CORS preflight OPTIONS request. Rate limiting and server errors return other 4xx or 5xx statuses.
/sendtx is submission only: it does not simulate or support other RPC methods. For rebroadcasting, see Best practices. For competitive priority fees, see getRecentPrioritizationFees.
Contact support by clicking the chat icon in your customer dashboard Sales questions? Contact us AI agent? Read llms.txt Follow updates: Blog · X · YouTube · Telegram · GitHub
Last updated