GET /nft/collections/{slug}/ohlc
GET

/v1/nft/collections/{slug}/ohlc

Collection OHLC chart data

AuthNone — works without a key

Request

GEThttps://api.xrpl.to/v1/nft/collections/fuzzybears/ohlc
Path parameterValueDescription
slugA collection slug, or its identity as issuer:taxon
Query parameterValueDescription
limitint (max 1000, default 365; legacy daily mode)
offsetint
resolution5|15|30|60|240|D|W
range1D|5D|1M|3M|1Y|ALL
cbint candle count (max 2000)
tounix ms (with resolution): a page of history, the cb candles that open before it; page back by passing the first candle's time, an empty ohlc means the history ends there
chgbool: each row also carries [change, change %] against the bar before
habool (with resolution): Heikin Ashi candles (TradingView's), warmed up on the bars before the window
indindicators instead of candles (with resolution, not to), as /ohlc/{id}?ind= takes them, on the floor candles
fromunix ms (with ind): the first bar wanted; default the last cb
tailint (with ind): only the last N bars
curl 'https://api.xrpl.to/v1/nft/collections/fuzzybears/ohlc'

Response

200Example response4 ms · just now · 1.2 KB · 76 lines
https://api.xrpl.to/v1/nft/collections/fuzzybears/ohlc
{
  "success": true,
  "took": 2,
  "collection": {
    "slug": "fuzzybears",
    "name": "Fuzzybears",
    "cid": "33920d4b2f0346fba52ece9f05c54f5f"
  },
  "ohlc": [
    {
      "bo": 650,
      "bof": 0,
      "c": 20,
      "h": 170,
      "l": 7,
      "lo": 6212,
      "o": 170,
      "s": 321,
      "t": "2025-03-21",
      "tr": 3958,
      "v": 17695.468614
    },
    {
      "bo": 615,
      "bof": 0,
      "c": 23.61864,
      "h": 24,
      "l": 0.001,
      "lo": 724,
      "o": 20,
      "s": 185,
      "t": "2025-03-22",
      "tr": 117,
      "v": 8589.362945
    },
    {
      "bo": 403,
      "bof": 0,
      "c": 1.96822,
      "h": 30,
      "l": 1.96822,
      "lo": 404,
      "o": 23.61864,
      "s": 100,
      "t": "2025-03-23",
      "tr": 65,
      "v": 4798.124488
    },
    {
      "bo": 268,
      "bof": 0,
      "c": 1.96822,
      "h": 1.96822,
      "l": 1.96822,
      "lo": 367,
      "o": 1.96822,
      "s": 106,
      "t": "2025-03-24",
      "tr": 33,
      "v": 7712.317392
    },
    {
      "bo": 305,
      "bof": 0,
      "c": 1.96822,
      "h": 1.96822,
      "l": 0.98411,
      "lo": 416,
      "o": 1.96822,
      "s": 106,
      "t": "2025-03-25",
      "tr": 111,
      "v": 8659.164528
    }
  ]
}

Long arrays and strings are shortened in the example; Send request for the full answer.

Shapeas documented
{
  success,
  collection,
  interval,
  ohlc: [
    [
      time,
      open,
      high,
      low,
      close,
      volume,
      sales,
      topSale,
      change?,
      changePct?
    ]
  ]
}; with ind: {
  success,
  interval,
  interval_seconds,
  vs_currency,
  t,
  indicators: [
    { id, inputs, offsets, plots, graphics? }
  ]
}

What it does

Collection OHLC chart data

A collection is its slug, or its on-chain identity as issuer:taxon. Each NFT in it comes back with its NFTokenID, the id every NFT endpoint takes. Go to NFT →
OpenAPI