> 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-tgm-flow-amounts.md).

# 29 Oct 2026: TGM flow amount fields

`POST /api/v1/tgm/flows` now returns `total_inflows_amount` and `total_outflows_amount`. Both contain token quantities, not transaction counts. The underlying calculations and signs are unchanged. Outflows are negative, except Hyperliquid sell sizes remain positive.

Use the new names in responses, filters and sorting. Amount filters accept decimal bounds. The old `total_inflows_count` and `total_outflows_count` names remain compatible and are deprecated. Requests using the old filter names receive a `Warning: 299` header. If both old and new filter names are supplied, their bounds must match or the request returns 422.

The deprecated `total_inflows_count` and `total_outflows_count` response fields, filters, and sort names will be removed on January 29, 2027.


---

# 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-tgm-flow-amounts.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.
