ZaaS HTTP API
HTTP API doc for ZaaS API
Last updated
Was this helpful?
HTTP API doc for ZaaS API
Last updated
Was this helpful?
https://zap-api.kyberswap.com/{chain} where chain is one of the . For example: https://zap-api.kyberswap.com/arbitrum
Please contact to whitelist your client id with more rate limit quota
Client Id
zap-docsRequest Id
Build encoded data for zap-in transaction from the specified route.
the wallet sending the transaction, and thus, the tokens.
the wallet receiving the new position. default to sender if empty.
the route as returned from get-route endpoint.
^(?:[A-Za-z0-9+/]{4})*(?:[A-Za-z0-9+/]{2}==|[A-Za-z0-9+/]{3}=)?$deadline for the swap transaction to execute.
the source of the zap-in transaction.
Build encoded data for zap-migrate transaction from the specified route.
the wallet sending the transaction, and thus, the tokens.
the wallet receiving the new position. default to sender if empty.
the route as returned from get-route endpoint.
^(?:[A-Za-z0-9+/]{4})*(?:[A-Za-z0-9+/]{2}==|[A-Za-z0-9+/]{3}=)?$deadline for the swap transaction to execute.
the source of the zap-migrate transaction.
whether to throw away the position NFT or keep it.
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
DEX_UNISWAPV3Possible values: id of the pool to zap into.
0x2f5e87c9312fa29aed5c179e456625d79015299cid 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.
120000max tick of the position, required if creating a new uniswapV3 position.
480000which 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
0xEeeeeEeeeEeEeeEeEeEeeEEEeeeeEeeeeeeeEEeEamount(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
1000000000000000000whether 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%.
100Client Id
zap-docsRequest Id
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
DEX_UNISWAPV3Possible values: 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
DEX_UNISWAPV3Possible values: id of the pool to zap into.
id of the pool to zap into.
id of the position to withdraw from
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.
liquidity amount to withdraw, or empty or 0 to withdraw all
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
options for getting aggregator routes 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%.
100Client Id
zap-docsRequest Id
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
DEX_UNISWAPV3Possible values: id of the pool to withdraw from.
id of the position to withdraw from
liquidity amount to withdraw, or empty or 0 to withdraw all
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
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%.
100Client Id
zap-docsRequest Id
Build encoded data for zap-out transaction from the specified route.
the wallet sending the transaction, and thus, the tokens.
the wallet receiving the new position. default to sender if empty.
the route as returned from get-route endpoint.
^(?:[A-Za-z0-9+/]{4})*(?:[A-Za-z0-9+/]{2}==|[A-Za-z0-9+/]{3}=)?$deadline for the swap transaction to execute.
the source of the zap-out transaction.
whether to throw away the position NFT or keep it.