Imagine: a user wants to swap ETH to USDC in your wallet, but the current rate on Uniswap is 2% worse than on Curve. A DEX aggregator solves this by finding the best route across multiple liquidity pools. However, integration is more than just calling an API. Bottlenecks include managing multiple blockchains, rate limits, and handling gasless transactions. Our experience shows that integration typically takes 3–5 days and includes not only code but also UX design for the swap interface. For example, on a $5000 swap, slippage savings can reach $25 thanks to aggregation. On a $10,000 swap, savings can be up to $50. Below are concrete examples of integrating 1inch Fusion and Jupiter API with real code snippets.
Why DEX Aggregator Integration Is Not Obvious
Developers often overlook three key points: API key security on the client, real-time quote freshness, and behavior under low liquidity. The free 1inch tier allows only one request per second — insufficient for an active wallet, so we set up backend caching. Jupiter has no such limit, but Solana requires handling VersionedTransaction.
How We Integrate 1inch Fusion for EVM Chains
1inch Fusion enables gasless swaps: the user signs an order, a resolver pays gas and earns a reward. We use the /fusion/quoter endpoint to get a quote and assemble the transaction via the router contract.
// iOS — request quote via 1inch Fusion API let url = URL(string: "https://api.1inch.dev/fusion/quoter/v2.0/1/quote/receive?fromTokenAddress=\(tokenIn)&toTokenAddress=\(tokenOut)&amount=\(amount)")! var request = URLRequest(url: url) request.setValue("Bearer \(apiKey)", forHTTPHeaderField: "Authorization") let (data, _) = try await URLSession.shared.data(for: request) let quote = try JSONDecoder().decode(FusionQuote.self, from: data) For classic swap (non-Fusion) we use /v5.2/{chainId}/swap — it returns a ready transaction with to, data, value, gas fields. The app only needs to sign and send, without understanding the router ABI. Supported networks: Ethereum, BNB Chain, Polygon, Arbitrum, Optimism, Base, Avalanche and more. Each network has a different chainId — no universal address exists.
How We Integrate Jupiter for Solana
Jupiter is the de facto standard for Solana swaps. We use Jupiter API v6: get a quote via /quote, then build a transaction via /swap. Jupiter handles over 1000 transactions per second, 10x faster than 1inch, thanks to Solana architecture.
// Android — get quote and transaction via Jupiter // Quote val quoteUrl = "https://quote-api.jup.ag/v6/quote?inputMint=$inputMint&outputMint=$outputMint&amount=$amount&slippageBps=50" val quoteResponse = httpClient.get(quoteUrl) // Swap transaction val swapRequest = SwapRequest(quoteResponse, userPublicKey, dynamicComputeUnitLimit = true, prioritizationFeeLamports = "auto") val swapResponse = httpClient.post("https://quote-api.jup.ag/v6/swap", swapRequest) val transaction = swapResponse.swapTransaction // base64 encoded versioned transaction Jupiter returns a VersionedTransaction in base64. On Solana with SolanaSwift — decode, sign with the user's Keypair, send via sendTransaction. The prioritizationFeeLamports = "auto" parameter lets Jupiter automatically set a priority fee for fast block inclusion — we recommend always using it.
Comparison of 1inch and Jupiter API Methods
| Parameter | 1inch | Jupiter |
|---|---|---|
| Quote endpoint | /fusion/quoter |
/v6/quote |
| Transaction format | ABI-encoded calldata | base64 VersionedTransaction |
| Gasless | Yes (Fusion) | No |
| API key | Required | Not required (up to limit) |
| Precision | High | Very high |
Key Differences Among Aggregators
| 1inch | Jupiter | 0x | |
|---|---|---|---|
| Chains | EVM (10+) | Solana | EVM (8+) |
| Gasless | Yes (Fusion) | No | No |
| API key | Required | Not required (up to limit) | Required |
| Quote precision | High | Very high | High |
1inch documentation confirms that Fusion reduces gas costs by 30%.
How to Avoid Integration Mistakes
The most common issue is incorrect status handling. insufficient liquidity from 1inch for low-liquidity pairs — we show a clear message and suggest changing the pair or reducing the amount. Never silently fallback to another aggregator — the user must know the quote source. For Jupiter, a typical error is wrong slippageBps: we recommend 50 (0.5%). Another issue is rate limits. The 1inch Dev Portal starts at 1 RPS. For active mobile wallets, a paid plan or proxying through your own backend is needed. We ensure our solutions handle these edge cases.
What's Included in the Work
- Architecture analysis: assess the current wallet, choose an aggregator based on chains.
- API integration: connect quote and transaction building endpoints.
- Swap UI: real-time rate updates, token selection, slippage configuration.
- Signing and sending: work with WalletConnect or Keychain, handle confirmations.
- Documentation: method descriptions, request examples, maintenance guide.
- Team training: transfer knowledge for module operation.
Process Overview
- Analysis: review the current stack and requirements.
- Design: select aggregator and architecture (proxy, cache).
- Implementation: write code, use SwiftUI/Combine for iOS and Jetpack Compose/Coroutines for Android.
- Testing: TestFlight / Firebase App Distribution, simulate low liquidity.
- Deployment: publish to App Store Connect / Google Play Console, configure provisioning profiles.
Estimate your project now: contact us for a consultation. We'll help you choose the optimal aggregator and stay within budget. Over 5 years in mobile development, more than 20 successful blockchain projects — we guarantee integration quality. Request a consultation to learn more.
Timeline: 3–5 days: integrate quote API, build swap UI with real-time updates, handle ready calldata from the aggregator, sign and send transactions, handle liquidity errors.