RecipientPatch
Every field is optional; only fields present are changed. `type` must not be present at all. `name`/`default`/`events`/`config` each reject an explicit JSON `null`. Changing `config.address` on a `type=email` recipient resets it to `status:"pending"` (old confirm/unsubscribe links stop working, a new confirmation is sent) and records `recipient.updated` with `changes.address: {"changed": true}` — never the old or new address itself. For `type=slack` (issue #359), `config.url` and `config.channel` are each independently optional — at least one is required when `config` is present — and changing either records `changes.url: {"changed": true}` (never the URL text) and `changes.channel: {"old": ..., "new": ...}` respectively, and cancels the recipient's own still-queued deliveries. Setting `config.channel` to `null` or `""` clears the override. For `type=pagerduty` (issue #363), `config.integration_key` is required when `config` is present; changing it records `changes.integration_key: {"changed": true}` (never the key itself) and cancels the recipient's own still-queued deliveries — it does not resolve an incident the old key already opened in PagerDuty.
Properties
JSON Schema
Work with this as data
Every JSON Schema here is available over the APIs.io API and to AI agents over MCP.