Skip to main content
GET
/
2
/
token
/
ohlcv-history
Get token OHLCV history
curl --request GET \
  --url https://demo-api.mobula.io/api/2/token/ohlcv-history
{
  "data": [
    {
      "v": 123,
      "o": 123,
      "h": 123,
      "l": 123,
      "c": 123,
      "t": 123
    }
  ]
}

​
FAQ

Mobula’s period is not the same format as TradingView’s ResolutionString. Treat them as different contracts and map values in your datafeed before calling Mobula.Often maps cleanly (Mobula normalizes case):
  • Seconds: TV 1S, 5S, … → Mobula 1s, 5s, …
  • Minute numerals: 1, 5, 15, 30 → 1m, 5m, 15m, 30m
  • Hour-style minute counts: 60 → 1h; 240 → 4h; 360 → 6h; 720 → 12h
  • Days / weeks: 1D → 1d, 1W → 1w
Important mismatch — TV 1M (one month):
TradingView uses 1M for one month. Mobula lowercases the string, so 1M becomes 1m, which means one minute, not one month. Never forward TV’s monthly resolution unchanged.Not a direct match:
  • Tick bars (1T, 5T, …) — Mobula serves time-based OHLCV candles, not tick aggregation.
  • Unrecognized strings — fall back to a default period (commonly 1h for unknown non-empty values, or the endpoint’s own default such as 5m when period is omitted).
Supported candle periods for this endpoint (canonical):
1s, 5s, 15s, 30s, 1m, 5m, 15m, 30m, 1h, 4h, 6h, 12h, 1d, 1w.
Aliases such as 5min or 60 → 1h are accepted by the API layer. Do not use 1month / TV-style monthly here: they normalize to 1M, which this OHLCV history service does not support.Recommendation: Add an explicit tradingViewResolutionToMobulaPeriod(resolution) (or equivalent) in your integration instead of passing TV resolutions straight through.

Query Parameters

​
address
string
required
​
chainId
string
required
​
from
​
to
​
period
string
​
amount
number | null
​
usd
default:true

Response

200 - application/json

Token OHLCV history response

​
data
object[]
required