Start Here

Everything you need before your first API call

KyberSwap provides three APIs for building on-chain trading and liquidity features - the Aggregator API for instant token swaps, the Zap as a Service (ZaaS) API for streamlined liquidity provision, and the Limit Order API for gasless and price-conditional trades. This section covers everything that applies across all three: how to choose the right API, usage limits, supported chains, and the core solutions behind how they work.

Which API Should I Use?

KyberSwap offers 3 APIs. Find your use case in the table below.

I want to...	Use this
Swap token A → token B at the best available rate	Aggregator API
Swap token A → token B at a price I set	Limit Order API
Add liquidity to a supported pool using any token	Zap as a Service API
Remove liquidity and receive a single token	Zap as a Service API
Migrate from a position to a new position	Zap as a Service API
Fill open limit orders as a taker or arbitrage bot	Limit Order API

• KyberSwap Aggregator API: Provides developers with more fine-tuned control when integrating swap functionality within their app. We provide guidelines and code samples on how to query and execute swaps at the favourable rates.

  • KyberSwap Widget: Plug and play superior rates directly from your app with just a few lines of code. Our endlessly customizable widget enables integrators to seamlessly blend superior rates into their dApps with easily configurable trade routes, fees, and themes.

• Limit Order API: A set of Maker and Taker APIs enables gasless management of limit orders secured by the option to settle on-chain. When settling orders on-chain, KyberSwap Limit Order provides the relevant APIs required to encode the call data to be sent to the Limit Order smart contracts.

• KyberSwap Zap as a Service (ZaaS): An API that streamlines decentralized liquidity provision. Powered by KyberSwap Aggregator, Zap minimizes price impact and employs fallback logic to execute additional swaps when necessary - maximizing capital efficiency and reducing failure rates, even during volatile market conditions.

Rate Limits & Client ID

KyberSwap APIs do not require authentication. Include x-client-id header in every request, using your app or company name as the value. Refer to Rate Limits & Client ID for further details.

Supported Chains & Networks

All KyberSwap APIs are EVM-only. Each API is available on a different subset of chains. See Supported Chains & Networks for the full list, including the chain identifier strings required in API paths.

Foundational Solutions

A short set of solutions that explain why the APIs are designed the way they are - covering trade routing, off-chain relay, and gasless approvals. If you're new to KyberSwap's architecture, read these before integrating. See Foundational Solutions.