Rango Docs


Rango exchange provides a versatile API that helps dApps and wallets get free from hassles of connecting to dozens of blockchains, tracking transactions, verifying third-party providers, etc. The whole idea behind our API is to make it the easiest possible solution on the market.
The API consists of just a few endpoints that have abstracted away a very huge amount of complexity in the server's side, such that making a fully-working cross-chain dApp over cosmos, Ethereum-based blockchains and UTXOs is a piece of cake.
Before diving into the details, here are some links to the technical specifications of the API, in the swagger format:


Our service is currently free. But to use our API endpoints, you should request an API key, describing your dApp, the blockchains you like to connect to, and your dApp domain if it's a website to enable CORS headers for your API key. You should attach your API key to all your request as:
curl 'https://api.rango.exchange/path/to/resource?apiKey=<YOUR-API-KEY>'


Rango currently supports around 40 blockchains as the source or the destination, including multiple Cosmos-compatible blockchains, Ethereum-based L1 & L2, Solana, and traditional UTXO as BTC, LTC, BCH, etc.
At the current stage, we might only return 4 different types of objects which support all these blockchains. The client doesn't mostly need to do any modifications to the response and should just send it to the wallet.
These four types include:
  1. 1.
    EVM Transaction: If the source of a step is an Ethereum compatible blockchain including Ethereum Mainnet, BSC, Avalanche, Harmony, Fantom, etc. we return an EVM transaction that contains a hex data and value that should be directly passed to the wallet to execute.
  2. 2.
    Transfer Transaction: If the source of a step is a UTXO blockchain that supports simple operations like transfer, a Transfer type of transaction is returned that contains the amount, symbol, destination wallet address, etc.
  3. 3.
    Cosmos Transaction: If the source of a step is Cosmos-based [Including Akash, Osmosis, Terra, Binance Chain (BNB)], then the result will be a Cosmos transaction that contains a list of Cosmos messages that should be passed to a wallet like Keplr.
  4. 4.
    Solana Transaction: It covers different models of transactions needed for Wormhole, Jupiter, and etc.
There will be more types as Rango expands its territory to more blockchains. You can find the details of these types on the Meta endpoint described in the SDK.


For any more information on how to use the API, contact Uchiha Sasuke from our dev team.