Account events

Account events are about your side — your reseller accounts, your registrar balances, your infrastructure. They fire independently of any specific registration task or domain. Typical use cases: oncall alerts, finance-team notifications, autorefill triggers.

balance.low

Fires each time a provider's balance crosses a new threshold going down. The ladder is $1000 → $500 → $200 → $100 → $50 → $10 — you get one event per step, not one event when the balance first becomes "low". This way you can wire different severities to different channels: a gentle Slack ping at $1000, a PagerDuty alert at $50.

Each threshold is re-armed as soon as the balance recovers above it — typically after you top the provider up. The next time it drops below, the alert fires again.

Code
{
  "event": "balance.low",
  "data": {
    "providerId": "cm3x4prov001",
    "providerName": "Spaceship Main",
    "providerType": "SPACESHIP",
    "balance": "47.08",
    "threshold": 50,
    "currency": "USD",
    "source": "live"
  },
  "timestamp": "2026-04-11T09:00:00.000Z"
}

Fields you care about:

• threshold — which step of the ladder was just crossed (1000, 500, 200, 100, 50, or 10). Drive your severity routing off this value, not off balance.
• source — "live" when the value came from the registrar's API, "approx" when it was computed from manual bookkeeping (sum(deposits) − sum(completed orders)). Use this to flag alerts from registrars without a balance endpoint (Webnic, Spaceship) so you know the number is an estimate, not ground truth.
• currency — currently always "USD". Thresholds are in USD too.

Check cycle runs every 5 minutes, plus once at worker startup. There is no daily dedupe cap — the re-arming logic handles dedupe naturally (you only get a new event when you cross a step you haven't been below already).