> 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/27-10-2026-unappliable-filters-rejected.md).

# 27-10-2026: Filters That Cannot Be Applied Return HTTP 400

Some endpoints accepted a filter that they could not apply to the request and answered with HTTP 200, as if the filter were not set. These requests now return HTTP 400 with `"error": "InvalidFilterError"` and the field names in `invalid_filters`, so a filter is either applied or rejected.

What this means for your requests:

* `POST /api/v1/perp-screener`: metric filters must exist for the selected `filters.trader_type`. For example, `smart_money_longs_count` without `"trader_type": "sm"` now returns 400. See [Perp Screener](https://docs.nansen.ai/api/hyperliquid/perp-screener.md) for the filters each mode supports.
* `POST /api/v1/tgm/pnl-leaderboard` and `POST /api/v1/tgm/perp-pnl-leaderboard`: `filters.token_price` now filters on `price_usd`. It was ignored before, so a request that sends it may now return fewer rows.
* Smart Money, Token God Mode and Profiler filters that select data rather than filter rows, such as `include_stablecoins`, `include_native_tokens`, `include_smart_money_labels`, the `tgm/transfers` flags and `hide_spam_tokens`, are unchanged. They were applied before and still are.


---

# 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/27-10-2026-unappliable-filters-rejected.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.
