Skip to main content
Support for Universal Router version 1.2 has been sunset. The Universal Router 1.2 has been replaced by the Universal Router 2.0. What changed? The API no longer accepts 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 default to 2.0. Why did this change? Universal Router 1.2 was replaced by Universal Router 2.0 in 2023. Universal Router 2.0 provides a more flexible routing framework which includes support for routing to V4 Uniswap Protocol pools. Universal Router 2.0 also reduces quote latency. What do I need to do? If you are still setting the x-universal-router-version header in your requests, you must update the value you submit to 2.0. If you do not provide the header, requests will automatically route to Universal Router 2.0. 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 protocols 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 with Universal Router 2.0, quotes return new Permit2 messages to sign to allow Permit2 to transfer tokens to Universal Router 2.0.