> 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/30-10-2026-who-bought-sold-total-and-net-volume.md).

# 30-10-2026: Who Bought/Sold: trade\_volume\_usd Is Total Volume, New Net Volume Fields

**Affected endpoint:** `POST /api/v1/tgm/who-bought-sold`

**Breaking change:** `token_trade_volume` and `trade_volume_usd` now return total volume, bought plus sold. They previously returned net volume (bought minus sold for `BUY`, sold minus bought for `SELL`). Sorts and filters on these two fields now use total volume too.

Net volume moves to two new fields, `net_token_volume` and `net_volume_usd`, which can also be used in sorts and filters. If you used `token_trade_volume` or `trade_volume_usd` as net volume, in the response, `order_by` or `filters`, switch to the `net_*` fields.

The default sort is now `net_token_volume` descending. It ranks rows exactly as before, because `token_trade_volume` held net token volume.

Which addresses are returned is unchanged: `BUY` lists addresses whose net token volume is zero or greater, and `SELL` the same for selling.

Example, one address on the `BUY` side:

| Field               | Before  | Now     |
| ------------------- | ------- | ------- |
| `bought_volume_usd` | 120,694 | 120,694 |
| `sold_volume_usd`   | 118,540 | 118,540 |
| `trade_volume_usd`  | 2,154   | 239,234 |
| `net_volume_usd`    | —       | 2,154   |


---

# 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/30-10-2026-who-bought-sold-total-and-net-volume.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.
