> 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/16-11-2026-hyperliquid-ohlcv-batch-errors.md).

# 16-11-2026: Hyperliquid OHLCV Batch Requests Report Failed Tokens

**Affected endpoint:** `tgm/token-ohlcv` with `chain` `hyperliquid`, batch requests (`token_addresses`)

A Hyperliquid batch request fetches each token separately. Until now, a token whose fetch failed, for example because the upstream price data provider was rate limiting requests, was left out of `tokens` and the request still returned 200. You could not tell a failed fetch from a token with no data.

**What changes in responses**

* Batch responses have a new `errors` array. Each entry has the `token_address` as submitted, a `reason` and a human-readable `message`. The other tokens are still returned in `tokens`.
* `reason` is one of:
  * `rate_limited`: the upstream provider is rate limiting requests. Retry later.
  * `unknown_token`: the provider has no data for this symbol. Check that it is correct.
  * `upstream_error`: the provider returned an error or could not be reached. Retry later.
  * `internal_error`: the request failed on our side.
* `errors` is an empty array when every token was fetched, and on every other chain.
* When every token in the batch fails, the request now returns the error status that a single-token request for the first submitted token returns (for example 422 for an unknown symbol), instead of 200 with an empty `tokens` array.
* Single-token requests are unchanged.

**Action required:** none. To retry only the tokens that failed, read `errors` and resend those with a `reason` of `rate_limited` or `upstream_error`.


---

# 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/16-11-2026-hyperliquid-ohlcv-batch-errors.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.
