GET
/
market
/
pairs
curl --request GET \
  --url https://api.mobula.io/api/1/market/pairs
{
  "data": {
    "pairs": [
      {
        "address": "<string>",
        "token0": {
          "address": "<string>",
          "decimals": 123,
          "symbol": "<string>",
          "name": "<string>",
          "logo": "<string>",
          "price": 123,
          "priceToken": 123,
          "id": 123
        },
        "token1": {
          "address": "<string>",
          "decimals": 123,
          "symbol": "<string>",
          "name": "<string>",
          "logo": "<string>",
          "price": 123,
          "priceToken": 123,
          "id": 123
        },
        "liquidity": 123,
        "volume": 123,
        "price": 123,
        "protocol": "<string>",
        "blockchain": "<string>",
        "exchange": "<string>",
        "factory": "<string>"
      }
    ]
  }
}

Query quick start

Input in “asset” the name of the asset you want to query, or the contract address while adding the blockchain as a second parameter. The market data asset query pattern is explained in great details here, with blockchain format, etc.

Data details

Price data is computed using Octopus, Mobula’s market data engine. You can have a high-level overview of how it’s computing DeFi prices here.

Protocols covered right now includes: Uniswap V2 and all +800 forks, Uniswap V3 and all +30 forks, Balancer V2/V3 (and forks), TraderJoe 2.1, Camelot stableswaps & all SUI DEXes.

Pairs are sorted by volume, then by liquidity - sent 25 by 25, use offset parameter to iterate over them (contact us if you need a higher limit).

Query Parameters

asset
string
required

The asset you want to target - asset name only works for assets listed on Mobula.

blockchain
string

Blockchain of the asset - only mandatory if asset is sent as smart-contract.

offset
integer

The offset of the results

Response

200 - application/json
data
object