Skip to main content
Infery sends operational notifications to channels you configure per workspace.

​
Channels

TypeSetupTypical payload
EmailAny member can subscribe themselves; admins can subscribe the whole workspaceFormatted HTML with event details
SlackIncoming webhook URL from Slack → paste into Settings → NotificationsBlocks-style message, colour-coded by severity
WebhookHTTPS endpoint of your choiceRaw JSON, signed with HMAC for verification

​
Events you can subscribe to

  • Budget thresholds — 50 / 75 / 90 / 100 % of monthly allowance consumed
  • Topup completed — successful payment
  • Payment failed — card declined, need to update billing
  • Quota exceeded — specific API key hit RPM/TPD/budget limit
  • Model deprecated — one of your referenced model slugs is scheduled for removal
  • Fallback triggered (rate) — fallback events above a threshold per hour (prod-alerting signal)
  • File quota reached — storage is full
  • Subscription changes — upgrade/downgrade, cancellation, renewal
  • Member invites — accepted / declined
  • Security — new API key created, key revoked, suspicious login

​
Per-member subscriptions

Each member picks their own subset of events on Settings → Notifications. You don’t spam billing-role people with dev events, and you don’t send Slack-only people their daily usage summary by email.

​
Webhook format

{
  "id": "evt_01J...",
  "type": "budget.threshold_reached",
  "workspace_id": "ws_...",
  "created_at": "2026-04-15T21:14:00Z",
  "data": {
    "threshold_pct": 75,
    "credits_used": 7500,
    "monthly_allowance": 10000
  }
}
Verify the X-Infery-Signature header against your webhook secret (HMAC-SHA256 of the raw body).

​
Suppressing notifications

Pause a channel from Settings → Notifications → channel row → Pause. Events stop delivering to that channel while it’s paused; history remains.