Skip to content
Error codes · Monitors, checks & agents

RU-3007: Invalid notification channel request

The request body for creating or updating a notification channel was refused: not JSON, failing field validation, or a config the channel type's own validator rejected (wrong host for a Discord or Teams webhook, a non-https endpoint, a missing Opsgenie key or region). The `error` field says which.

On the wire

Ships with HTTP status 400, carrying "code": "RU-3007" in the response body alongside the human-readable error message. Existing fields are never replaced by the code: it is additive.

Common causes

  • A `type` outside discord, msteams, opsgenie, generic_json (sms, voice and mobile_push are not yet deliverable).
  • A `config` missing the key the type needs: webhookUrl (discord, msteams), url (generic_json), apiKey and region (opsgenie).
  • An endpoint that resolves to a private or internal address.

How to fix it

  1. Read the `error` field for the failing field.
  2. Compare the config keys against the API docs at /docs/api, "POST /notification-channels".

Related codes

  • RU-3008: Notification channel not found
  • RU-3009: Duplicate notification channel name

Still stuck?

Ask support and mention RU-3007: the code pins down the exact refusal path, so you skip the diagnostic back-and-forth.