Query Details
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.Parameter | Type | Required | Description |
---|---|---|---|
asset | string | Yes | The asset identifier to query. This can be the token’s name or the contract address. |
blockchain | string | Cond. | The blockchain network name or ID where the asset resides. Required if querying by contract address. |
shouldFetchPriceChange | string (e.g., “24h”) | No | Timeframe for price change calculation. Example: "24h" returns price change over the last 24 hours. |
symbol | string | Cond. | Token ticker symbol. If duplicates exist, returns the first match. Use contract + blockchain for accuracy. |
id | number | Cond. | The Asset Unique Identifier to query. |
Additional Notes
- Data Freshness: Market data is constantly recomputed, in real time. There is no delay except how fast we ingest blocks, which is usually 100-200ms after blocks are emitted.
-
Pricing Model 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.
volume
is on-chain volume, andoff_chain_volume
is - as name implies, the off-chain volume. -
On some long tail assets,
price is different than on CoinGecko or CoinMarketCap. Why?
Mobula uses market-depth-weighted average price, which is more accurate than the simple average price. This is especially important for assets with low / zero volume in the long tail. -
How to query native tokens?
To query the native token of any given chain, useasset=0xEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEE&blockchain=<blockchain_name or blockchain_id>
Usage Examples
- Query by Asset Name
- Query by Contract Address of Token.
- Query by Query Native Token.
- Query by Asset id.
Query Parameters
Available options:
24h
Response
200 - application/json
Market data response