Skip to main content
We will be sunsetting support for Universal Router version 1.2 in the API on July 22, 2025. The Universal Router 1.2 has been replaced by the Universal Router 2.0 which is already available through the API. What is changing? The API will no longer accept the header x-universal-router-version with value 1.2. Requests to any API endpoint with the header set to 1.2 will be met with an error. Requests to any API endpoint which do not specify the x-universal-router-version will be defaulted to use 2.0. Why is this changing? Universal Router 1.2 has been replaced by Universal Router 2.0 since 2023. Universal Router 2.0 provides a more flexible routing framework which includes support for routing to V4 Uniswap Protocol pools. Shifting to Universal Router 2.0 will also reduce quote latency. What do I need to do? If you currently set the x-universal-router-version in your requests, you must update the value you submit to 2.0. If you do not provide the header, you will automatically start routing to Universal Router 2.0 after the sunset date. Additionally, whether or not you provide the header you may need to do any or all of the following:
  • If you do not specify protocols today and do not want to route to V4 pools, you will need to specify potocols and include V2 and/or V3 as parameters. More details on how the protocols field works are available in the Swap Routing Guide.
  • If you whitelist the Universal Router contract address, you will need to whitelist new addresses for Universal Router 2.0. The list of addresses is available in the Supported Chains & Tokens Guide.
  • Be aware that after upgrading to Universal Router 2.0, quotes will return new Permit2 messages to sign to allow Permit2 to transfer tokens to Universal Router 2.0.
⌘I