Home › Migrate from 1inch

Migrate from 1inch API to swapapi

Last updated:

TL;DR

swapapi is a drop-in alternative to 1inch's Swap API. No API key, no SDK, no account. One GET request returns the same calldata you're used to — across 46 EVM chains instead of ~10.

Motivation

Why developers switch

API key registration

1inch requires creating an account and generating an API key before making any requests. swapapi requires nothing — start with a curl command in 30 seconds.

Restrictive rate limits

1inch rate limits vary by plan. The free tier is restrictive and paid plans can be expensive for high-volume applications. swapapi has generous rate limits with no paid tiers.

Breaking API changes

1inch changed their swap endpoint from GET to POST, breaking existing integrations. swapapi uses a simple GET request and maintains backward compatibility.

Zero setup

No SDK installation, no account creation, no environment variables. swapapi works with raw HTTP from any language, any platform, any autonomous agent.

Parameter mapping

Translating parameters

Most parameters map directly. The main differences are naming and slippage format.

1inch Parameter swapapi Parameter Notes
src tokenIn Same format (0x address)
dst tokenOut Same format (0x address)
amount amount Same (raw units, no decimals)
from sender Same (wallet address)
slippage maxSlippage 1inch: 1-50 (percentage). swapapi: 0-1 (decimal). 1inch slippage=1 is swapapi maxSlippage=0.01
Authorization header (not needed) swapapi requires no authentication

Code comparison

Before and after

1inch (before) 
$ curl -X GET \
  "https://api.1inch.dev/swap/v6.0/1/swap" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  --data '{
    "src": "0xEeee...EEeE",
    "dst": "0xA0b8...eB48",
    "amount": "1000000000000000000",
    "from": "0xd8dA...6045",
    "slippage": 1
  }'
swapapi (after) 
$ curl "https://api.swapapi.dev/v1/swap/1?\
  tokenIn=0xEeee...EEeE&\
  tokenOut=0xA0b8...eB48&\
  amount=1000000000000000000&\
  sender=0xd8dA...6045"

# No API key
# No headers
# No request body
# Just a GET request

Response format

Response differences

swapapi wraps every response in an envelope with a success flag and timestamp. The transaction data is structurally similar.

1inch response 
{
  "tx": {
    "from": "0xd8dA...6045",
    "to": "0x...router",
    "data": "0x...calldata",
    "value": "1000000000000000000",
    "gas": 250000                     // number — unsafe for large values
  }
}
swapapi response 
{
  "success": true,                             // always check this first
  "data": {
    "status": "Successful",                  // "Successful" | "Partial" | "NoRoute"
    "swapPrice": 2847.53,                    // exchange rate
    "priceImpact": 0.0012,                   // 0.12% as decimal
    "amountIn": "1000000000000000000",       // string — BigInt safe
    "expectedAmountOut": "2847530000",      // string — BigInt safe
    "tx": {
      "from": "0xd8dA...6045",
      "to": "0x...router",
      "data": "0x...calldata",
      "value": "1000000000000000000",
      "gas": "250000"                       // string — BigInt safe
    },
    "rpcUrls": ["https://..."]             // bonus: RPC endpoints for the chain
  },
  "timestamp": "2026-03-20T..."              // ISO 8601
}

Key differences: swapapi adds a success envelope, a status field (Successful/Partial/NoRoute), price impact data, and RPC URLs. All BigInt values are returned as strings to prevent JavaScript precision loss.

Honest tradeoffs

What you gain and what you lose

What you gain

  • No authentication overhead — no keys, no headers, no secrets
  • 46 EVM chains (vs ~10 on 1inch)
  • BigInt-safe string serialization for all large numbers
  • Built-in RPC URLs in every response
  • AI-agent ready — designed for autonomous systems
  • Consistent JSON envelope with status and price impact

What you lose

  • No Fusion mode (gasless swaps via resolvers)
  • No limit orders API
  • No portfolio/balance tracking API
  • No cross-chain swaps (for that, consider Li.Fi)

Checklist

Migration checklist

Follow these steps to complete your migration. Most integrations can be migrated in under 15 minutes.

  • Replace base URL: api.1inch.dev/swap/v6.0/{chainId} to api.swapapi.dev/v1/swap/{chainId}
  • Remove Authorization header
  • Rename src to tokenIn
  • Rename dst to tokenOut
  • Rename from to sender
  • Convert slippage: divide by 100 (e.g., slippage=1 becomes maxSlippage=0.01)
  • Update response parsing: unwrap response.data.tx instead of response.tx
  • Test with a small amount first

Need more details? Read the full integration tutorial. See how swapapi compares to other APIs in the comparison table. Check all 46 supported chains. Learn about slippage and price impact.