read.internal.notification_template

What WOULD be sent for one type, on one channel, in one language — resolved through the same three layers the send path uses (store → tenant → factory), with the layer that answered, the channel’s field shape, the type’s variables, the shared blocks its wording may include (name -> source, the very set the send path registers) and the “the default changed since your edit” signal with both sides of the diff. Internal face only.

• Surface: GET /v1/read/internal/notification_template · MCP tool read.internal.notification_template
• Auth: ★ Internal read (operator) — a tenant credential is REQUIRED; requires the tenant.settings.read scope. The tenant is resolved from the CALLER’s identity, never from store. Personal fields come back MASKED for an actor without pii.read (the shape is unchanged).

Params (JSON Schema)

{
  "properties": {
    "channel_key": {
      "minLength": 1,
      "type": "string"
    },
    "locale": {
      "maxLength": 35,
      "minLength": 2,
      "type": "string"
    },
    "store": {
      "minLength": 1,
      "type": "string"
    },
    "type_key": {
      "minLength": 1,
      "type": "string"
    }
  },
  "required": [
    "type_key",
    "channel_key",
    "locale"
  ],
  "type": "object"
}

Result (200)

Open (unknown) — this capability does not declare an output schema.

Errors

validation_failed (400) · not_found (404) · unauthorized (401) · forbidden (403)