> 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/17-11-2026-input-defaults-and-aliases.md).

# 17-11-2026: date Is Optional on Four Endpoints; 24h and the Zero Address Accepted

Three kinds of request that returned HTTP 422 now work.

## `date` defaults to the last 30 days

`date` is now optional on these endpoints. Without it, the request covers the 30 days up to and including today (UTC), the same default as [`POST /api/v1/profiler/address/pnl`](https://docs.nansen.ai/api/profiler/address-pnl-and-trade-performance.md):

* [`POST /api/v1/tgm/who-bought-sold`](https://docs.nansen.ai/api/token-god-mode/who-bought-sold.md)
* [`POST /api/v1/tgm/flows`](https://docs.nansen.ai/api/token-god-mode/flows.md)
* [`POST /api/v1/tgm/pnl-leaderboard`](https://docs.nansen.ai/api/token-god-mode/pnl-leaderboard.md)
* [`POST /api/v1/profiler/address/pnl-summary`](https://docs.nansen.ai/api/profiler/address-pnl-and-trade-performance.md)

A request that sends `date` works as before. A request without it is charged the endpoint's usual credits.

## Timeframes in other units

[Flow Intelligence](https://docs.nansen.ai/api/token-god-mode/flow-intelligence.md) and [Token Information](https://docs.nansen.ai/api/token-god-mode/token-information.md) accept `timeframe: "24h"` as `"1d"`. The [Token Screener](https://docs.nansen.ai/api/token-god-mode/token-screener.md) accepts `"1d"` as `"24h"`. A timeframe longer than the endpoint offers now says which is the longest, for example "Timeframe '30d' is not available on this endpoint. The longest is '7d'."

## The zero address as the native token

On EVM chains, `token_address: "0x0000000000000000000000000000000000000000"` is now read as the native-token placeholder `0xeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee` on token endpoints that accept native tokens, such as Flow Intelligence and Token Information. Endpoints that reject native tokens, and wallet fields, still reject it. See [Native Tokens](https://docs.nansen.ai/reference/native-tokens.md#the-zero-address-also-means-native).


---

# 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/17-11-2026-input-defaults-and-aliases.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.
