EVM Swaps
KyberSwap Aggregator EVM APIs
Last updated
Was this helpful?
KyberSwap Aggregator EVM APIs
Last updated
Was this helpful?
Note on integration: clientID
In order to continuously improve the KyberSwap Aggregator, our APIs implement a client identifier field that enables us to understand how the APIs are being utilized. A stricter rate limit will be applied if a clientId is not provided. As a developer integrating with our APIs, please preferably use the same clientID (i.e. company name or your app name) for:
[V1] Get Swap Route
Header: x-client-id
[V1] Post Swap Route For Encoded Data
Header: x-client-id
This will enable us to serve you better as we continuously strive to improve our Aggregator API. For integrators who have previously integrated with our Legacy API, we highly encourage migrating to the Latest APIs to ensure access to the latest features as well as improved service quality and efficiency.
Example
[V1] GET /routes
Header
x-client-id: MyAwesomeApp
[V1] POST /route/build
Header
x-client-id: MyAwesomeApp
To support more performant queries and the use of RFQ liquidity sources, KyberSwap highly encourages all integrators to implement the latest API [V1] version. While both versions of the API remains backwards compatible, only the [V1] APIs will continue to receive updates and can make use of RFQ liquidity sources, and hence developers are highly encouraged to implement the latest [V1] APIs to avoid any disruptions as the non-versioned API will eventually be deprecated.
If you're just getting started with the KyberSwap Aggregator, you can refer to our dev guide for information and code samples on how to query and execute swaps at superior rates. Note that there is also a option for integrators who require a simple minimal-code implementation. For existing integrators, please refer to for further details on the motivation behind the upgrade as well as the relevant changes to swap flow and parameters.
For every swap executed by the KyberSwap Aggregator, users will be able to see an estimated output amount based on the current price as well as a minimum received that takes into account the . KyberSwap Aggregator will always strive to execute swaps at the estimated output amount and revert the transaction if the minimum received amount is not achieved.
Note that this surplus is different from fees as it only applies in cases where the executed swap rate is better than the estimated rate at point of transaction confirmation. Please refer to for more information.
Find the best route to swap from tokenIn to tokenOut, supporting all liquidity sources including RFQ. Use this API to get a route preview before confirming the swap. The route returned can then be combined with transaction specific params in the POST API payload to get the encoded data for submission to the KyberSwap router contract. Refer to for the full list of supported networks.
Chain name. Full list of supported chains available in Docs.
ethereumAddress of the input token
0xEeeeeEeeeEeEeeEeEeEeeEEEeeeeEeeeeeeeEEeE in case of native token
Address of the output token
0xEeeeeEeeeEeEeeEeEeEeeEEEeeeeEeeeeeeeEEeE in case of native token
Amount of the input token (in wei)
DEX IDs included in the route, separated by comma
DEX IDs excluded from the route, separated by comma
Exclude unscalable sources and only use sources that accept scaling input amounts
Determines whether to only return single-path route
Determines whether gas costs are accounted for when searching for best route
Custom gas price in wei used when searching for the best swap route. Use result from eth_gasPrice otherwise
Fee amount(s) to be collected.
If isInBps = true, feeAmount is the percentage of fees to take with base unit = 10000, i.e feeAmount = 10 and isInBps = true then fee = 0.1%;
If isInBps = false, feeAmount is the amount of token to take as fee, i.e feeAmount = 10 and isInBps = 'false' then fee = 10 token weis.
It also accepts a comma-separated list of numbers to support multiple fee receivers, for example: feeAmount=10,20
Indicates that the API client wants to charge fee by input token (currency_in) or output token (currency_out).
Default is empty whereby no fee is charged.
if true, fee is taken in bps of the amount in/out, instead of absolute wei value
The API client's wallet address(es) to receive fee (if chargeFeeBy is not empty). It can accept a comma separated list of addresses to collect multiple fee amounts into multiple addresses
ClientID of the party calling the API. Provide a value to identify your client and avoid getting rate limited. If an even higher rate limit is needed, contact bd.
MyAwesomeAppRetrieve the information about a Swap between 2 tokens with encoded data to submit to KyberSwap router contract. RFQ liquidity sources are not supported. Please refer to for the full list of supported networks.
Full list of supported chains available on Docs.
Address of the input token
0xEeeeeEeeeEeEeeEeEeEeeEEEeeeeEeeeeeeeEEeE in case of native token
Address of the output token
0xEeeeeEeeeEeEeeEeEeEeeEEEeeeeEeeeeeeeEEeE in case of native token
Amount of the input token (in wei)
DEX IDs included in the route, separated by comma
Exclude unscalable sources and only use sources that accept scaling input amounts
Determines whether gas costs are accounted for when searching for best route
Custom gas price in wei used when searching for the best swap route. Use result from eth_gasPrice otherwise
This is the amount of slippage the user can accept for his trade. The unit is bps (1/100 of 1%). The value is in ranges [0, 2000], with 10 meaning 0.1%, and 0.1 meaning 0.001%. If no value is provided, slippageTolerance will be set to 0.
Indicates that the API client wants to charge fee by input token (currency_in) or output token (currency_out).
Default is empty whereby no fee is charged.
The API client's wallet address to receive fee (if chargeFeeBy is not empty)
if true, fee is taken in bps of the amount in/out, instead of absolute wei value
Fee amount to be collected.
If isInBps = true, feeAmount is the percentage of fees to take with base unit = 10000, i.e feeAmount = 10 and isInBps = true then fee = 0.1%;
If isInBps = false, feeAmount is the amount of token to take as fee, i.e feeAmount = 10 and isInBps = 'false' then fee = 10 token weis
Deadline (in Unix epoch second) for the transaction to be executed by. Default will be +20 minute. Cannot be in the past.
1744196804Address to receive the output token
Json string to include your client id in the source field if header cannot be used
{"source":"MyAwesomeApp"}Referral info to include in the swap transaction's ClientData event.
Encoded token's permit calldata to swap without approving. The permit's spender should be the routerAddress returned in the Get Swap Route API response. See /permit
If true, the slippage tolerance can be any value. Please use with caution.
ClientID of the party calling the API. Provide a value to identify your client and avoid getting rate limited. If an even higher rate limit is needed, contact bd.
MyAwesomeAppSwap Found
Get the swap's calldata to be sent to the KyberSwap router contract. The request body must contain the routeSummary as exactly returned by [V1] Get Swap Route along with the additional tx related parameters. Please refer to for the full list of supported networks.
Chain name. Full list of supported chains available on Docs.
ethereumClientID of the party calling the API. Provide a value to identify your client and avoid getting rate limited. Please use the same ClientID as the source field in the body.
Address from which the swap input tokens will be transferred from
Address to which the swap output tokens will be sent to
Encoded token's permit calldata to swap without approving. The permit's spender should be the routerAddress returned in the Get Swap Route API response. See /permit
Deadline (in Unix time second) for the transaction to be executed. Default will be +20 minute. Cannot be in the past.
This is the amount of slippage the user can accept for his trade. The unit is bps (1/100 of 1%). The value is in ranges [0, 2000], with 10 meaning 0.1%, and 0.1 meaning 0.001%. If no value is provided, slippageTolerance will be set to 0.
If true, the slippage tolerance can be any value. Please use with caution.
If true, call eth_gasEstimate to get gas estimation for the transaction. Also helps to detect any potential reverts.
The source of the swap to be recorded on-chain. You should use (and it defaults to be) the same value as the x-client-id in the header, unless you want to track separate sources.
Referral info to include in the swap transaction's ClientData event.
