Notifications

Notification preferences control which events trigger an email to which contact, and which trigger a webhook delivery instead (or in addition). Categories include billing alerts, security events, quota warnings, scheduled-maintenance announcements, and feature releases.

The defaults are sane — billing and security always go to the billing/security contact regardless of preferences. The configurable categories are operational ones: maintenance windows, quota thresholds, beta-feature announcements, etc.

For larger teams the typical pattern is to route operational notifications via webhooks into your incident-management system (PagerDuty, Opsgenie) rather than email to a single contact. The webhook route here uses the same delivery semantics as the webhooks doc.

What's next

Webhooks — the delivery channel for non-email routing.
Account overview — where the billing and security contacts live.

No endpoints to show

The OpenAPI spec doesn't currently expose any endpoints under thenotificationstag. This is usually a manifest typo; check that the tag matches what the backend serves at /openapi/external.json.

Edit this page on GitHub