Supported Chains & Tokens

Supported Chains for Swapping

The following chains are supported for swapping. Note the router address, which you may need to whitelist for your wallet(s)/application.

For the avoidance of any doubt, the most up to date list of routers is available in GitHub here.

Support for Universal Router 2.0 and 2.1.1 ends on October 21, 2026. See Sunset of Universal Router 2.0 and 2.1.1.

Universal Router version

The Trading API builds swap calldata for a specific Universal Router version. Select the version with the x-universal-router-version request header, accepted on /quote, /swap, /swap_5792, and /swap_7702.

Default version

When you do not send the x-universal-router-version header, the API defaults to Universal Router 2.1.2 on every chain that has a 2.1.2 deployment. zkSync has no 2.1.2 and runs 2.0 only. zkSync's 2.0 Universal Router address is 0x28731BCC616B5f51dD52CF2e4dF0E78dD1136C06.

You can always set the header explicitly. Requesting a version a chain does not support returns an error, for example 2.0 on Robinhood Chain and Arc, neither of which has a 2.0 deployment.

The table above lists the 2.1.2 address for each chain. The default can change over time, so set the header explicitly when you need a stable target.

SDK compatibility for decoding calldata

Use at least the SDK version that introduced support for the router version you decode, and pass its UniversalRouterVersion member to the parser:

Versions 5.12.0 and later are the first to resolve 2.1.2, and the first to carry the current 2.2.0 addresses. Earlier releases resolve 2.2.0 to a deployment that was replaced, so do not use them for that version.

From 2.1.1 onward, the V2 and V3 swap commands carry an extra minHopPriceX36 per-hop slippage array, and the v4 swap actions have the same field. SDK 5.9.0 is the first release whose parser decodes that array and the first whose parseCalldata accepts a UniversalRouterVersion argument, which defaults to V2_0. Older SDKs may parse newer calldata without an error but drop minHopPriceX36, so your validation can be incomplete even when it appears to succeed.

import { CommandParser, UniversalRouterVersion } from '@uniswap/universal-router-sdk'

// `calldata` is the value returned by the /swap response.
// The version you pass must match the x-universal-router-version header you sent.

// Defaults to V2_0. On 2.1.1 and later calldata the per-hop slippage array is
// silently dropped, and on SDK < 5.9.0 there is no version argument to fix it.
const parsedWrong = CommandParser.parseCalldata(calldata)

// SDK >= 5.12.0: pass the matching version so 2.1.2 calldata decodes fully.
const parsed = CommandParser.parseCalldata(calldata, UniversalRouterVersion.V2_1_2)

Track the SDK releases so your decoder stays compatible when the router version changes. The current mapping lives in the SDK constants file.

UniswapX Chain Support

UniswapX is available on the following chains:

If you submit a quote request with protocols set to UNISWAPX_V2 or UNISWAPX_V3 on a chain not listed above, the request will fail.

Most integrators do not need to set protocols. With the default BEST_PRICE routing preference, the API considers UniswapX alongside the Uniswap Protocol and selects the most efficient route based on current inputs. Set protocols only to narrow routing to a specific protocol or UniswapX version. See AMM vs UniswapX routing for details.

How Do I Swap Native Tokens?

To swap native tokens, use the address 0x0000000000000000000000000000000000000000.

If the native token is the input token and you want the quote request to consider UniswapX routes, set the optional x-erc20eth-enabled header to true on the /quote request. This enables native ETH input support for UniswapX via ERC20-ETH (EIP-7914) on supported wallets and chains. Use the same header when submitting the resulting UniswapX order to /order.

curl -X POST https://trade-api.gateway.uniswap.org/v1/quote \
  -H "x-api-key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json" \
  -H "x-erc20eth-enabled: true" \
  -d '{
    "tokenIn": "0x0000000000000000000000000000000000000000",
    "tokenOut": "0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48",
    "tokenInChainId": 1,
    "tokenOutChainId": 1,
    "amount": "1000000000000000000",
    "type": "EXACT_INPUT",
    "swapper": "0x..."
  }'

Supported Tokens for Swapping

Generally any two tokens on any supported chain can be swapped. However, Uniswap Labs maintains a list of "unsupported" tokens, for which we do not permit swapping through any method due to legal or regulatory restrictions. Those tokens and their chains are available here: https://unsupportedtokens.uniswap.org/. If one or both tokens in the swap pair are on the unsupported token list, no quote will be returned.

Note that all tokens do not necessarily have regular or sufficient liquidity to perform a swap between any two tokens at any volume. We always recommend submitting a quote request prior to performing a swap to confirm that there is an available route, or filler, to complete the swap and available liquidity.

We recommend that end users always do their own due diligence before swapping any tokens.

Supported Tokens for Bridging

To get a list of tokens which can be bridged, and the chains between which they can be bridged, make a request to the swappable_tokens endpoint.

How Often Are New Tokens Added?

As new tokens are created they are automatically detected and made available for swapping within minutes of creation. New tokens may not be immediately swappable as it is dependent on there being sufficient liquidity in a pool for swapping to take place.

The Verified tokens list is updated periodically as new tokens are supported by major centralized exchanges.