notification.channel.set_enabled

Switch one channel on or off for one message type, for the whole tenant or for one store. Switching ON is refused when the resolved template is missing a field the channel declared required — the general rule behind “WhatsApp does not enable without an approved template name”.

• Scope: tenant.settings.write
• System: no
• Reachable from: POST /v1/commands/notification.channel.set_enabled (tenant credential) · MCP tool notification.channel.set_enabled · SDK client.call('notification.channel.set_enabled', …)
• Events: notification.config.updated

Input (JSON Schema)

{
  "properties": {
    "channel_key": {
      "pattern": "^[a-z][a-z0-9_]*$",
      "type": "string"
    },
    "enabled": {
      "type": "boolean"
    },
    "locale": {
      "maxLength": 35,
      "minLength": 2,
      "type": "string"
    },
    "store_id": {
      "anyOf": [
        {
          "minLength": 1,
          "type": "string"
        },
        {
          "type": "null"
        }
      ]
    },
    "type_key": {
      "minLength": 1,
      "type": "string"
    }
  },
  "required": [
    "type_key",
    "channel_key",
    "enabled"
  ],
  "type": "object"
}

Result (200)

{
  "additionalProperties": false,
  "properties": {
    "channel_key": {
      "type": "string"
    },
    "enabled": {
      "type": "boolean"
    },
    "type_key": {
      "type": "string"
    }
  },
  "required": [
    "type_key",
    "channel_key",
    "enabled"
  ],
  "type": "object"
}

Errors

validation_failed (400) · unauthorized (401) · forbidden (403) · conflict (409) · internal (500)