> For the complete documentation index, see [llms.txt](https://docs.nansen.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nansen.ai/api/changelog/28-10-2026-ohlcv-range-includes-open-close.md).

# 28-10-2026: OHLCV Candle Ranges Include the Open and Close

**Affected endpoints:** `POST /api/v1/tgm/token-ohlcv` (single and batch requests) and `POST /api/v1beta1/tgm/historical-token-ohlcv`, every chain except `hyperliquid`

Every candle now satisfies `high >= max(open, close)` and `low <= min(open, close)`. The same applies to `market_cap.high` and `market_cap.low`. Previously the range could exclude the open: a sub-daily candle's open, and every candle's market-cap open, is the previous candle's close, and `5m` candles were a single price sample, so their `high`, `low` and `close` were equal.

**What changes in responses**

* `high` and `low` widen to include `open` and `close` where they did not. `open`, `close`, volume and timestamps are unchanged.
* `5m` candles have `high` and `low` equal to `open` and `close`, whichever is larger and smaller, instead of a single price.
* From `5m` upward, prices come from five-minute samples, so a range can still miss a move that reverses within five minutes. On every sub-daily timeframe the open is the previous candle's close, so after a gap (common for low-liquidity tokens) the range includes the price before the gap.
* On `1d`, `1w` and `1M`, price `high` and `low` are unchanged. `market_cap.high` and `market_cap.low` were previously equal to `market_cap.close` on `1d`, because they come from daily closing market caps. They now also include `market_cap.open`, the previous candle's closing market cap, so they change on almost every daily candle. They are not intraday market-cap extremes.
* Hyperliquid candles are unchanged; they come from the exchange.

**Action required:** none.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.nansen.ai/api/changelog/28-10-2026-ohlcv-range-includes-open-close.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
