# Messaging & Reach

> Transactional email, team notifications, custom sender domains and per-channel consent, with one delivery pipeline.

> Markdown version of https://kanorio.com/en/developers/products/messaging. Append `.md` to any developer docs URL for this format. Index: https://kanorio.com/llms.txt · MCP: https://app.kanorio.com/api/mcp

Status: **Available**

Messaging delivers what other products decide to send: order confirmations, form confirmations, course notices and team alerts. Each product decides when to notify; messaging delivers reliably and respects consent and suppression.

## How the APIs fit

- Configure sender domains, team recipients and notification content in the dashboard.
- Use [Automation](https://kanorio.com/en/developers/products/automation) to send messages when events happen.
- Webhooks warn you when a sending domain degrades, a quota runs low or a team destination is disabled.

There are no Management API operations for messaging today.

## What the APIs expose

| Capability | Status | API | Elements | Hosted site | Webhooks |
| --- | --- | --- | --- | --- | --- |
| Transactional notification scenarios (built-in automations), one send() pipeline, team recipients, custom sender domain, per-channel consent & suppression | Available | Management API `automations.list`, `automations.set_action_enabled` (scenario toggles); sending itself has no public API | — | `/automations/settings`, `/settings/email` | — |

## Webhook events

- `customers.sendingDomain.degraded`: Fired when a verified custom sender domain fails DNS verification and campaign sending is paused.
- `customers.messagingQuota.alert`: Fired when monthly messaging quota is exhausted, auto-upgraded, or add-on billing fails.
- `customers.teamDestination.disabled`: Fired when a team notification destination (webhook or email) is automatically paused after repeated delivery failures.

Payloads: https://kanorio.com/en/developers/webhooks/events

## For site owners

Dashboard help: https://kanorio.com/en/help/email-settings