> 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/24-09-2026-wallet-address-field-name.md).

# 24-09-2026: wallet\_address Is the Name for a Wallet Input

Some endpoints use `address` for the wallet that a request is about, and other endpoints use `wallet_address`. We now use `wallet_address` as the one name for this input. New endpoints use only `wallet_address`.

These endpoints now accept `wallet_address`. The old `address` field is deprecated on them:

| Endpoint                                        | Before           | Now                                                            |
| ----------------------------------------------- | ---------------- | -------------------------------------------------------------- |
| `POST /api/v1/profiler/address/pnl-summary`     | `address`        | `wallet_address` (`address` is deprecated)                     |
| `POST /api/v1/profiler/address/related-wallets` | `address`        | `wallet_address` (`address` is deprecated)                     |
| `POST /api/v1/portfolio/defi-holdings`          | `wallet_address` | `wallet_address` (`address` is accepted as a deprecated alias) |

What this means for your requests:

* Requests that send only `address` continue to work. The response includes a `Warning: 299` header that tells you to use `wallet_address`.
* You can send both fields only if they contain the same address. If they contain different addresses, the request fails with status 422.
* The responses do not change.

Change `address` to `wallet_address` on these endpoints. We will continue to accept `address` until at least December 23, 2026. Other endpoints that use `address` do not change yet.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.nansen.ai/api/changelog/24-09-2026-wallet-address-field-name.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.