Get the best zap-in route.

Refer to https://docs.kyberswap.com/kyberswap-solutions/kyberswap-zap-as-a-service/zaps-supported-chains-dexes for list of supported dexes for each chain

id of the pool to zap into.

id of the position to add liquidity to; omit to create a new uniswapV3 position. for uniswapV2 this is user address

min tick of the position, required if creating a new uniswapV3 position.

max tick of the position, required if creating a new uniswapV3 position.

which token(s) to use as zap source. also accepts comma separated addresses

amount(s) to zap including fee, corresponding to tokenIn. also accepts comma separated amounts.

which token(s) to use as zap source. also accepts comma separated addresses. deprecated: use tokens_in. if both fields are specified, they are combined

amount(s) to zap including fee, corresponding to tokenIn. also accepts comma separated amounts. deprecated: use amounts_in. if both fields are specified, they are combined

whether to disable swapping with the aggregator

comma-separated list of sources to use for aggregator

comma-separated list of sources to exclude for aggregator

comma-separated list of pools to exclude for aggregator

the address of the fee recipient.

fee percentage in per cent mille (0.001% or 1 in 100,000). Ignored if feeAddress is empty. From 0 to 100,000 inclusively. Example: 1 for 0.001%.

maximum slippage tolerance in basis points (0.01%), used for aggregator (exceeding which the transaction will revert) and pool swap during zap (for additional zapping and for refund). From 0 to 10,000 inclusively. Example: 1 for 0.01%.

Client Id

Request Id