What is the rate limit?
As of August 2023, all public API usage has been reduced to 1 requests per second (rps). For increased limits, please visit https://portal.1inch.dev to apply for an enterprise endpoint.
Please note: All 1inch Network API users must now register and obtain an API key at https://portal.1inch.dev/.
Troubleshooting "Insufficient Liquidity" error
This error can occur for a number of reasons:
The liquidity pool has not been queried - make sure one of the aggregated sources has at least 10k of a connector token listed below.
If you're getting a quote, please make sure to take into account the decimals of the token. Do not include decimal places in the "from token amount". The API returns the number of decimal places the token supports when calling
There's an error in the server and is unable to find a path, this may require contacting the 1inch support team for more investigation.
Troubleshooting "Cannot Estimate"
This error occurs when the
eth_estimateGas RPC call throws an error. There are many reasons why this can throw an error, and they all tend to mean the transaction is guaranteed to fail. This is a protection, so a transaction is broadcast that's going to fail. To find the precise error, disableEstimate=true can be used in the query and an
eth_estimateGas RPC call can be done locally. The transaction can also be simulated with a platform like tenderly or blocknative for a better look at the transaction trace.
Some common reason why a transaction may fail:
A token has a fee on transfer or swap and the slippage tolerance needs to be increased
A token has a fee on transfer and the fee and referrer parameter is set causing the transaction to always fail
The rate has expired and changed in the latest block.
Troubleshooting insufficient allowance / balance
In the case of one of these errors, you may not have a token approval or you're missing the token balance. To do a token approval, you can use the API to approve the token to the 1inch router.
What are the "parts" parameters?
The parts parameters is comprised of 3 things
Each of these has their own unique meaning. The main route parts denotes the initial split and can be seen on the UI. In this example it's the 70%/30% split
The parts parameter is how many individual blocks there can be. In the picture above we can see 4 blocks with the top being the first main route part with 2 parts to it and the bottom one being the second main route part with 2 parts in it.
The virtual parts is the splits inside of a part. We can see in the first main route part above, in the first block there are 2 virtual parts splitting the USDC between hashflow and uniswap. In the second main route part we can see three virtual parts in the first block, a hashflow route with 2 different rates and one to uniswap.
What is the "Complexity level?"
Complexity level is how many steps a swap can go through, below are the levels and what it means for the swap. Each level adds to the previous level.
Complexity level 0 - the source token can be wrapped or unwrapped and swapped through one liquidity pool per main route part.
Complexity level 1 - the source token can be wrapped or unwrapped and swapped through two liquidity pools. This means there can be up to one connector token in each main route part.
Complexity level 2 - the source token can be wrapped or unwrapped and swapped through three liquidity pools. This means there can be up to two connector tokens in each main route part. This is the default setting
Complexity level 3 - the source token can be wrapped or unwrapped and swapped through four liquidity pools. This means there can be up to three connector tokens in each main route part.
How can I limit the liquidity sources in the query?
To limit the liquidity sources to a query, select them using the "protocols" parameter as a CSV list of liquidity sources.
Still have questions?
Reach out to the community on https://discord.com/invite/1inch or search around communities like stack overflow or github