> 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-smart-money-perp-trades-only-new-positions.md).

# 27-10-2026: Smart Money Perp Trades only\_new\_positions Works Without filters and Narrows Other Filters

Until now, `POST /api/v1/smart-money/perp-trades` ignored `only_new_positions: true` when the request body had no `filters` object (or `"filters": null`). Those requests returned every trade (Open, Add, Reduce and Close) without any error. Sending `"filters": {}` made the flag work.

**`only_new_positions: true` now returns only Open Long and Open Short trades whether or not `filters` is sent.** Credit costs are unchanged.

The flag also now narrows `filters.side`, `filters.action` and `filters.type` like any other filter, instead of adding to them. A trade must match all of them:

| Request                                                      | Before                                    | Now                                         |
| ------------------------------------------------------------ | ----------------------------------------- | ------------------------------------------- |
| `only_new_positions: true` with `"side": "Long"`             | every Long trade plus Open Short trades   | Open Long trades only                       |
| `only_new_positions: true` with `"type": "Limit"`            | every Limit trade plus Market Open trades | Limit Open Long and Limit Open Short trades |
| `only_new_positions: true` with `"action": "Buy - Add Long"` | Add Long trades plus every Open trade     | no trades                                   |

Filters that cannot all hold at once, such as `"side": "Long"` with `"action": "Sell - Open Short"`, return an empty `data` list. With `only_new_positions: true` they used to return every Open trade.

An empty `filters.action` list (`[]`) is now treated as not set, like an empty `filters.side` list. It used to return no trades.

If you sent `"filters": {}` to work around the first issue, you can keep doing so or drop it.


---

# 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-smart-money-perp-trades-only-new-positions.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.
