AnyInt Docs
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

ChannelBest for
email notificationshuman review and finance or security alerts
webhooksautomation 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.generated
  • billing.paid
  • billing.overdue
  • usage.alert
  • usage.limit_reached
  • member.invited
  • member.joined
  • member.removed
  • key.created
  • key.disabled
  • key.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.

On this page