> 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-tgm-holders-label-filters.md).

# 27-10-2026: Token Holders Applies include\_smart\_money\_labels

`POST /api/v1/tgm/holders` accepted `filters.include_smart_money_labels` but did not apply it: the response held every holder for the chosen `label_type`. `filters.exclude_smart_money_labels` was also ignored in some cases. Both filters now take effect, or the request returns HTTP 400 with `InvalidFilterError`.

What this means for your requests:

* `include_smart_money_labels` now narrows the result to holders with at least one of the given labels. A request that sent it before may now return fewer rows.
* With a `label_type` other than `all_holders`, every label in `include_smart_money_labels` must belong to that type. For `smart_money` that is `Smart Trader` or `Fund` (the [deprecated](https://docs.nansen.ai/api/changelog/14-10-2026-dated-smart-trader-labels-deprecation.md) dated Smart Trader labels are also accepted). For example, `label_type: "exchange"` with `["Smart Trader"]` now returns 400. The response lists `invalid_labels` and `supported_labels`.
* Label filters return 400 with `aggregate_by_entity: true` and on bitcoin, which always aggregates by entity. They were ignored there before.
* For native tokens and major stablecoins with `label_type: "all_holders"`, `exclude_smart_money_labels` on its own returns 400. It was ignored there before. `include_smart_money_labels` works there, can be combined with `exclude_smart_money_labels`, and lifts that path's filter and sorting limits; see [Native Tokens](https://docs.nansen.ai/reference/native-tokens.md).
* An empty label list is treated as not set.

See [Token Holders](https://docs.nansen.ai/api/token-god-mode/holders.md) for an example.


---

# 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-tgm-holders-label-filters.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.
