> 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-smart-alert-masked-channels.md).

# 28-10-2026: Smart Alert Channel URLs Are Masked in Responses

Smart alert responses (list, create, update and toggle) now mask Slack, Discord and webhook channel URLs. Anyone who has one of these URLs can post to the channel, so they are no longer returned in full:

* Slack: `https://hooks.slack.com/services/T000/****`
* Discord: `https://discord.com/api/webhooks/123/****`
* Webhook: `https://****/****` (the port is kept, for example `https://****:8443/****`)

Webhook signing secrets were already not returned; responses show `hasSecret: true`. Telegram chat IDs are unchanged. Error responses mask channel URLs in the same way.

Alerts keep delivering to the full URL that you configured. Nothing changes for alerts that you have already set up.

**Updating alerts:** you can send a channel back exactly as a list response returned it. The masked URL is matched to the alert's stored channel and the full URL is kept, along with a webhook's secret. If a masked URL matches none of the alert's channels or more than one, the update returns HTTP 400; send the full URL instead, or omit `channels` to keep the current ones. Creating an alert with a masked URL also returns HTTP 400.

If you need a channel's full URL later, keep your own copy when you create the alert.


---

# 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-smart-alert-masked-channels.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.
