---
title: "Get Notification Channel"
description: "Returns one notification channel, in the same shape as an entry of List Notification Channels. Secrets in config are redacted."
---

`GET /api/notification-channels/{id}`

## Access

The same scope check as editing the channel, read-only: a website channel needs read access to that website, a customer channel needs that customer in your scope (a customer-scoped API token only reaches its own customer), an organization channel needs read access to the organization.

## Example (cURL)

```bash
BASE_URL="https://uptimeify.io"
TOKEN="<your-api-token>"

curl -X GET "$BASE_URL/api/notification-channels/42" \
  -H "Authorization: Bearer $TOKEN" \
  -H "Accept: application/json"
```

## Response

`200 OK`

```json
{
  "id": 42,
  "organizationId": 10,
  "customerId": 5,
  "websiteId": null,
  "type": "webhook",
  "category": "alert",
  "name": "Ops webhook",
  "config": {
    "webhookUrl": "https://hooks.example.com/t/1",
    "secret": "********"
  },
  "delaySeconds": 0,
  "conditions": null,
  "allowedPackageTypes": null,
  "isActive": true,
  "verifiedAt": null,
  "createdAt": "2026-06-01T08:00:00.000Z"
}
```

## Common errors

- `400 Bad Request` (`invalidChannelId`) when the id is not a positive number
- `401 Unauthorized` when you are not logged in
- `403 Forbidden` when the channel is outside your scope
- `404 Not Found` (`channelNotFound`) when the channel does not exist