> 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/05-10-2026-hyperliquid-ohlcv-date-only-end.md).

# 05-10-2026: Hyperliquid OHLCV Date-Only End Covers the Whole Day

**Affected endpoints:** `tgm/token-ohlcv` with `chain` `hyperliquid`, single and batch requests

A date-only `date.to` (for example `"2026-10-02"`) now covers that whole UTC day, the same as on every other chain. Previously, on Hyperliquid it ended at 00:00 UTC of that day, so the response stopped at the candle that opens at midnight.

**What changes in responses**

* A date-only `date.to` returns that day's candles through its last interval. For today, the last candle is the current one, which is still forming.
* A `date.from` later on the same day as a date-only `date.to` (for example `"2026-10-02T03:00:00Z"` to `"2026-10-02"`) now returns candles. Previously it failed with status 422.
* Timestamps are unchanged. A timestamp without an offset is read as UTC.
* The deprecated `date_range` field is unchanged.

**Action required:** to end at exactly 00:00 UTC, send that instant as a timestamp, for example `"2026-10-02T00:00:00Z"`.


---

# 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/05-10-2026-hyperliquid-ohlcv-date-only-end.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.