> 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/29-10-2026-date-range-offsets.md).

# 29-10-2026: Date Ranges With a Time-Zone Offset Query the Requested Time

**Affected endpoints:** every endpoint that takes a `date` range (`from` / `to`) or a date-range filter, such as `filters.block_timestamp`

A timestamp with a time-zone offset is now converted to UTC before the query runs. For example, `"from": "2026-10-27T20:00:00+08:00"` now covers 12:00 UTC, the same instant as `"2026-10-27T12:00:00Z"`.

Previously the offset was dropped, so that request covered 20:00 UTC instead, eight hours off, with no error.

**What changes in responses**

* Requests that send an offset such as `+08:00` or `-04:00` now return data for the time they asked for. An offset can move the date as well: `2026-10-27T23:30:00-05:00` is `2026-10-28 04:30 UTC`.
* Timestamps ending in `Z`, timestamps without an offset, and date-only values are unchanged. A time without an offset is read as UTC.
* Hyperliquid OHLCV requests already converted offsets and are unchanged.

**Action required:** if you sent local times with an offset and adjusted for the shifted results, remove that adjustment.


---

# 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/29-10-2026-date-range-offsets.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.
