Documentation Index
Fetch the complete documentation index at: https://dev.jup.ag/docs/llms.txt
Use this file to discover all available pages before exploring further.
/submit sends your signed transactions through Jupiter’s proprietary transaction landing infrastructure. This is the same infrastructure that powers Jupiter’s own swap products, now open to any integrator. It accepts any valid signed Solana transaction with a SOL tip, costs zero API credits, and works on all plans including keyless access.
Why /submit is competitive
Jupiter’s transaction landing stack is purpose-built for high throughput and low latency:- SWQoS via high-stake validator. Jupiter operates one of the highest-staked validators on Solana. Solana’s Stake-Weighted Quality of Service (SWQoS) reserves ~80% of a leader’s TPU capacity for staked validators proportional to their stake. Higher stake means more reserved bandwidth when forwarding transactions to the current leader.
- Beam (custom TPU forwarder). Jupiter’s own TPU client bypasses standard RPC nodes and sends transactions directly to leaders via staked QUIC connections. This removes intermediaries that could be malicious actors and eliminates RPC processing overhead.
- DoubleZero. Dedicated fiber network for validator communication, with FPGA-based spam filtering and transaction deduplication at the network edge. Cleaner transaction set, faster propagation between validators.
- Ultra-low-latency fiber. Private fiber links from Tokyo to Frankfurt reduce physical propagation time between Jupiter’s infrastructure and leader validators globally.
- High-performance, scalable infrastructure. Built to handle the volume of Jupiter’s own products, where millions of swaps land daily.
How it works
- Build your transaction (using
/build, or assemble your own) - Include a SOL tip transfer instruction (minimum 0.001 SOL) to one of 16 tip receiver accounts
- Sign the transaction
- POST the base64-encoded signed transaction to
https://api.jup.ag/tx/v1/submit
/build transactions, use the tipAmount parameter to have the tip instruction included automatically. For non-Jupiter transactions, add a standard SOL transfer instruction to one of the tip receiver accounts.
Requirements
| Requirement | Details |
|---|---|
| Valid signed transaction | Must be a valid Solana transaction with all required signatures |
| SOL tip | Minimum 1,000,000 lamports (0.001 SOL) transferred to one of the 16 tip receiver accounts |
| Transaction size | Must not exceed the Solana transaction size limit (1232 bytes) |
| API access | Works with any API key or keyless access |
Code example
Using /build
Use/build with the tipAmount parameter to automatically include a tip instruction in the response.
Adding tip instruction manually
For non-Jupiter transactions (another swap protocol, a program call, a transfer), add a standard SOL transfer to one of the 16 tip receiver accounts. Randomise which account you send to on each transaction to reduce write-lock contention.Best practices
- Randomise tip accounts: there are 16 tip receiver accounts. Randomise which one you send to on each transaction to reduce write-lock contention across concurrent submissions.
- Use
tipAmountwith/build: passtipAmountas a query parameter to have the tip instruction included automatically, rather than adding it manually. - Set
maxRetries: 0on RPC fallback: if you run/submitin parallel withsendRawTransaction, let your application control retry logic rather than the RPC node, so you can refresh the blockhash between attempts. - Poll for confirmation: use
confirmTransactionwith the blockhash andlastValidBlockHeightfrom your transaction. If the blockhash expires without confirmation, rebuild with a fresh blockhash and resubmit. /submitdoes not simulate: we send directly to the TPU for fastest possible delivery. If you require simulation, do it before making a request to/submit.- Colocate for lowest latency: Jupiter’s API gateway runs in six AWS regions. Deploy your servers in the nearest region to minimise round-trip time.
How /submit differs from /execute
/execute | /submit | |
|---|---|---|
| Paired with | /order (meta-aggregator flow) | /build or any signed transaction |
| Fee model | Jupiter swap fees (included in the order) | SOL tips (minimum 0.001 SOL) |
| Transaction source | Must match the exact transaction from /order | Any valid signed Solana transaction |
| Credit cost | 0 credits | 0 credits |
| Use case | Managed swap execution for /order transactions | Any transaction: /build swaps, non-Jupiter transactions |
API reference
Endpoint:POST https://api.jup.ag/tx/v1/submit
See the POST /submit API reference for the full specification.
Related
- Build: build custom transactions with
/build(usetipAmountfor automatic tip inclusion) - Order & Execute: the standard swap flow using
/order+/execute - Reduce Latency: use
mode=faston/buildfor faster routing - Plans and Pricing: all plans include
/submitat zero credit cost - Latency and Server Locations: API gateway regions and colocation guidance
