> 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-unknown-nested-fields.md).

# 28-10-2026: Unknown Pagination, Range and Sort Fields Return HTTP 422

Unknown keys in pagination objects, numeric and integer range filters, and sort-order objects now return HTTP 422 with `"code": "unknown_field"`. Previously, these keys could be silently ignored, causing requests to use default pagination or omit an intended filter.

The error response lists the valid fields for the affected object and identifies its location, including the index for a sort-order list item.

Check your requests for these common mistakes:

* Use `pagination.per_page`, not `pagination.perPage`.
* Use `min` and `max` inside range filters, not `mn` or `mx`.
* Use `field` and `direction` inside each `order_by` item, not `direc`.

Valid field names, default values, range bounds and sort directions are unchanged.


---

# 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-unknown-nested-fields.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.
