# Notification destination is not valid for its channel

> Canonical HTML: https://screenrig.ai/problems/notification-destination-rejected

HTTP 400 · `notification_destination_rejected`

## What it means

The API answers with HTTP 400 Bad Request and an `application/problem+json` document when the condition is Notification destination is not valid for its channel. The document's `type` member is `https://screenrig.ai/problems/notification-destination-rejected`, the address of this page, and its `code` member is `notification_destination_rejected`.

## What to do

Give the credential the service itself issues: a Slack incoming webhook URL, a Teams Workflows webhook URL, a PagerDuty Events API v2 routing key or a Telegram bot token. The detail names the shape the channel takes.

## Player action

This problem defines no Player action class. It belongs to a project, pairing or account flow that an agent or the dashboard drives.

## Reference

| Field | Value |
| --- | --- |
| Code | `notification_destination_rejected` |
| HTTP status | `400 Bad Request` |
| Type | `https://screenrig.ai/problems/notification-destination-rejected` |
| Player action | `none` |

- [All problem types](https://screenrig.ai/problems)
- [API reference](https://screenrig.ai/docs/api#problems)
- [Problem registry YAML](https://screenrig.ai/docs/api/problems.yaml)