---
title: "act: notification channel"
description: "Writes one notification channel, which is where a notice goes to The channel is ready once its test notice is acknowledged."
section: reference
address: /reference/act/notification_channel
contract: 0476e35e6e275db5
---

# act: notification channel

Writes one notification channel, which is where a notice goes to The channel is ready once its test notice is acknowledged.

[figure: The caller sends NotificationChannelInput to /v1/act/notification_channel. The platform returns a card whose body is NotificationChannel.]

<span class="op-method">POST</span><span class="op-path">/v1/act/notification_channel</span>

Write a notification channel. The call needs the user rung under a token with the act grant, and it is served by the platform.

The route takes [NotificationChannelInput](/concepts/notificationchannelinput) and returns a card whose body is [NotificationChannel](/concepts/notificationchannel).



## Request body
The request body is [NotificationChannelInput](/concepts/notificationchannelinput).



| field | type | required | note |
|---|---|---|---|
| `kind` | `one of in the app \| email \| Slack \| webhook \| the extension` | yes |  |
| `address` | `text` | yes |  |
| `notices` | `[text]` | yes |  |



## Response
The route returns a card whose body is [NotificationChannel](/concepts/notificationchannel). Every card ends with a foot that states the basis of each number, the scope of the call, and the time when the facts were true.

## Headers


| header | required | meaning |
|---|---|---|
| `Scale-Scope` | yes | the scope the call runs in: tenant/<id>, then /brand/<id>, then /strategy/<id> |
| `Scale-As-True-On` | no | the date the facts must have been true on; defaults to now |
| `Scale-As-Known-On` | no | the date the facts must have been known on; defaults to now |
| `Scale-Key` | no | for a change, the key made from the input; a repeat under the same key returns the unit held and writes nothing |



A caller needs the user rung and a token with the act grant. The platform serves this route.

## Example
The example sends the smallest body that NotificationChannelInput allows. The build validates it against the schema of NotificationChannelInput.

<details class="wire"><summary>Example</summary>





```sh
curl -X POST https://api.scaleintelligence.co/v1/act/notification_channel \
  -H "Scale-Key: $SCALE_KEY" -H "Scale-Scope: tenant/<id>" \
  -H "content-type: application/json" \
  -d '{ "kind": "in the app", "address": "…", "notices": [] }'
```




```typescript
import { client } from "@scale/sdk";
const answer = await client.act.notification_channel({
    "kind": "in the app",
    "address": "…",
    "notices": []
  });
// answer.body is a NotificationChannel. answer.foot holds the basis, the scope and the time.
```




```python
import requests
answer = requests.post("https://api.scaleintelligence.co/v1/act/notification_channel",
    headers={"Scale-Key": KEY, "Scale-Scope": "tenant/<id>"},
    json={
      "kind": "in the app",
      "address": "…",
      "notices": []
    }).json()
```




```rust
let answer: Card = client.post("https://api.scaleintelligence.co/v1/act/notification_channel")
    .header("Scale-Key", key).header("Scale-Scope", "tenant/<id>")
    .json(&NotificationChannelInput { /* the fields of the page */ }).send().await?.json().await?;
```




</details>

## MCP tool
The MCP tool `si.act.notification_channel` takes the same input and returns the same card. The tool changes data and needs a grant. An MCP host that renders cards draws this card from `ui://scale-intelligence/cards/NotificationChannel`. The [tool's page](/reference/tools/si-act-notification_channel) describes it.