> 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/28-10-2026-profiler-perp-positions-funding-sign.md).

# 28-10-2026: Profiler Perp Positions Funding Fields Use Negative for Paid

`POST /api/v1/profiler/perp-positions` returned funding with the opposite sign to the rest of the API: a positive `cumulative_funding_*_usd` value meant the position paid funding. `POST /api/v1/tgm/perp-positions` and the Nansen app use negative for funding paid.

Each position in `asset_positions[].position` now has three new fields that use the same sign as the rest of the API. **Negative means funding paid, positive means funding received.**

| Deprecated field (positive = paid)    | New field (negative = paid) |
| ------------------------------------- | --------------------------- |
| `cumulative_funding_since_open_usd`   | `funding_since_open_usd`    |
| `cumulative_funding_all_time_usd`     | `funding_all_time_usd`      |
| `cumulative_funding_since_change_usd` | `funding_since_change_usd`  |

Each new field has the same amount as the deprecated field next to it, with the sign flipped. For example, a long that paid $1,080,576 in funding since it was opened now returns `"funding_since_open_usd": "-1080576"` and `"cumulative_funding_since_open_usd": "1080576"`.

The deprecated fields keep their values and sign until they are removed, which will not happen before January 26, 2027. Switch to the new fields before then. Credit costs are unchanged.


---

# 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/28-10-2026-profiler-perp-positions-funding-sign.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.
