A Practical Guide to 1inch API Integration for Your dApp

Our service integrates 1inch API with your smart contracts, providing DEX aggregator functionality with gas optimization and support for 1inch Fusion. Users lose up to 10% on spread when manually searching across pools. Our 1inch API integration service delivers seamless DEX aggregation with optimal rates. Integrating the 1inch API (v6) solves this in 2–3 days: the protocol splits orders across 200+ liquidity sources to find the best rate. We handle integration, slippage configuration, approve processing, and testing — you get an aggregator with minimal time to market. Our track record: 5+ years in DeFi, 20+ DEX aggregator integration projects. Integration with 1inch API is 10x faster than building your own aggregator from scratch. With over 5 years of experience and 20+ successful integrations, we deliver reliable solutions. Estimated savings: $2,000–$5,000 per project compared to custom development.

Why 1inch API Integration Is Critical for DeFi Products

Users expect the best rate without manually searching pools. Integration via 1inch provides fast routing; a custom implementation would take weeks, while a ready-made solution takes days. The time and cost savings are significant: you get a battle-tested aggregator without developing and debugging your own router. Compared to using a single DEX, 1inch aggregation can reduce slippage by up to 5%.

Outdated Quotes and Slippage at Execution

GET /v6.0/1/quote returns toAmount — the expected output token amount. Time passes between receiving the quote and executing the transaction. In a volatile market, the price can shift 0.5–2% in 10–30 seconds.

If you pass slippage=1 (1%) to POST /v6.0/1/swap but the market moves 1.5%, the transaction reverts — the user paid gas and got nothing. The correct approach: dynamically set slippage based on pair volatility — 0.5% for stable pairs, 1–3% for volatile ones.

Another issue: toAmount from /quote may not match toAmount from /swap. This is normal — /swap builds the final calldata considering the current pool state. Showing the user the value from /quote while signing the transaction with /swap calldata is best practice.

Approve and Permit: Two Patterns

The 1inch Aggregation Router v6 accepts tokens via standard ERC-20.approve. But for a better UX, permit (EIP-2612) is also supported — a gasless approve via signature. If the token implements EIP-2612 (DAI, USDC on Ethereum, most modern ERC-20s), use the /approve/transaction endpoint only as a fallback.

To check permit support: call token.nonces(address) — if it doesn't revert, permit is supported.

A second type of approve is 1inch Permit2 (analogous to Uniswap Permit2). If the user has already given an approval to Permit2 for another protocol, no re-approval is needed. This improves UX for frequent swaps.

1inch API Integration: Step-by-Step Guide

Request Structure

The basic flow for a swap widget:

1. GET /v6.0/{chainId}/tokens — cache the list of supported tokens (once per hour is enough)
2. GET /v6.0/{chainId}/quote?src=...&dst=...&amount=... — get a quote, show it to the user
3. GET /v6.0/{chainId}/approve/allowance?tokenAddress=...&walletAddress=... — check current allowance
4. If allowance < amount: GET /v6.0/{chainId}/approve/transaction → sign the approve
5. POST /v6.0/{chainId}/swap → get calldata, send the transaction

For multichain support, use chainId in the URL. The 1inch API documentation describes all endpoints.

Error Handling

1inch v6 returns HTTP 400 with a JSON body for any business logic error. Typical codes:

Rate limiting must be handled with exponential backoff, not immediate retries.

Classic vs Fusion: Which to Choose?

For simple integration (swap widget, aggregator in a dApp) — Classic mode via REST API. For advanced UX with gasless transactions — Fusion.

Calldata Verification

Before sending the user's transaction, always simulate via eth_call. This catches reverts before gas is spent. In wagmi/viem:

const { data } = await publicClient.call({ account: userAddress, to: swapData.tx.to, data: swapData.tx.data, value: BigInt(swapData.tx.value), });