Documentation

Notifications

A prepaid balance that runs out stops your traffic. Threshold alerts tell you it is coming while there is still time to do something about it.

What sets off an alert

Kakehashi compares spending against a budget every fifteen minutes. When the proportion spent reaches a level you asked to be warned at, it sends one message to the channels you turned on.

Alerts are available on the budgets that have a limit to measure against:

Your own balance, on an individual account.
The organization's balance, for organization admins.
Each group's limit, for that group's admins and for organization admins.

Individual key budgets are not covered

A cap on a single key is not watched here. Alerts are about the balance and the group limits your traffic actually runs out of.

Setting thresholds

Open Notifications in the portal. Each budget you can manage gets its own card, with a Warn me at list.

The default is 80% if you never set one yourself.
You can set up to six levels, anywhere from 1% to 100% — say 50%, 80% and 95%, for a warning, a nudge and an alarm.
Each level fires once as spending climbs past it. If one check crosses several at once, you get a single message naming the highest.
A top-up lowers the proportion spent and re-arms the levels it dropped back below, so the same budget can warn you again later.

Alerts can read above 100%

The proportion is not capped. If spending overshoots a limit before the next check, the message says so rather than rounding down to a tidy 100%.

Email and Slack

Both channels are off until you turn them on. An account nobody has configured sends nothing — so if you want to be warned, this is the page to visit first.

The two notification channels and what each needs
Channel	What it needs	Who receives it
Email	Nothing, or a list of up to 20 addresses you choose.	By default, whoever can act on it: you, on an individual account; the organization's admins for the shared balance; a group's admins plus the organization's admins for a group limit. Plain members are not emailed.
Slack	An Incoming Webhook URL from your own Slack workspace.	Whichever channel that webhook posts to.

Setting up Slack

Create an Incoming Webhook in your Slack workspace and paste the URL — it has to be a https://hooks.slack.com/services/… address — into the Slack field, then turn Slack on. The URL is stored on our side and never shown back to the browser; the portal only reports whether one is configured.

Turning Slack on without a webhook is refused, rather than silently accepted and then quietly dropping every alert.

What the message says

Email and Slack carry the same text: which budget, how far through it you are, the level that was passed, and what is left. Amounts are in US dollars.

Subject: Kakehashi usage alert: the Acme group has used 80% of its budget

The Acme group has used 80% of its budget, passing the 80% level you
asked to be warned at.

Used: $80.00 of $100.00
Remaining: $20.00

Top up or adjust your alert threshold in the Kakehashi customer portal.

Sending a test

Each card has a Send test button. It pushes a sample alert through the real channel — same provider, same address, same webhook — so a test that arrives proves the whole path works, not merely that the settings saved.

At least one channel has to be on first. Tests are limited to a handful every ten minutes per budget; if you reach that, wait a moment and try again.

If a test fails

The portal shows a short reference code instead of the provider's own message. Quote that code to support and we can find the exact failure in the logs — see Errors and limits.

If alerts stop arriving

Check the channel is still switched on, and that the addresses are still right.
An address that has bounced, or has reported our mail as spam, is suppressed and will not receive further alerts until that is cleared. Slack is unaffected by this, which is a good reason to turn both on.
A budget with no limit has no proportion to measure, so it never alerts. Group alerts need the group to have a limit set.