Enterprise
Webhooks and Notifications
Enterprise customers need operational events pushed into their own systems instead of checking dashboards manually.
Enterprise customers need operational events pushed into their own systems instead of checking dashboards manually.
Delivery channels
| Channel | Best for |
|---|---|
| email notifications | human review and finance or security alerts |
| webhooks | automation and system-to-system handling |
Typical email notifications
- billing generated
- spend or usage warnings
- member changes
- security alerts
Webhook configuration model
The current enterprise plan describes three key fields:
- webhook URL
- subscribed event types
- signing secret
Example event areas
billing.generatedbilling.paidbilling.overdueusage.alertusage.limit_reachedmember.invitedmember.joinedmember.removedkey.createdkey.disabledkey.deleted
Integration checklist
Before depending on webhooks in production, confirm the webhook URL, subscribed event types, signing secret, retry behavior, and the event payload fields your system stores.