> 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/16-11-2026-token-deployment-dates-utc.md).

# 16-11-2026: Token Deployment Dates End in Z (UTC)

**Affected endpoints:** `POST /api/v1/token-screener`, `POST /api/v1/tgm/token-information`

Both endpoints returned the token deployment date without a timezone. The value was always UTC, but the response did not say so.

| Endpoint          | Field                                 | Before                | Now                    |
| ----------------- | ------------------------------------- | --------------------- | ---------------------- |
| Token Screener    | `token_deployment_date`               | `2025-03-01T12:34:56` | `2025-03-01T12:34:56Z` |
| Token Information | `token_details.token_deployment_date` | `2025-03-01 12:34:56` | `2025-03-01T12:34:56Z` |

**Both fields are now ISO 8601 strings in UTC with a trailing `Z` and second precision.** The time itself is unchanged: it is the same UTC instant as before, now marked as UTC. Token Information also changes the separator between date and time from a space to `T`.

What happens when no deployment time is available is unchanged: Token Screener can return `null`, and Token Information returns an empty string (`""`).

If your code parses the old value with a fixed format such as `%Y-%m-%dT%H:%M:%S` or `%Y-%m-%d %H:%M:%S`, change it to accept the new form (for example `%Y-%m-%dT%H:%M:%SZ`, or an ISO 8601 parser). Parsers that already read ISO 8601 with an offset need no change.


---

# 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/16-11-2026-token-deployment-dates-utc.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.
