Alert API

Everything the console does, from your own code

A REST API you can read in an afternoon: one key, one POST, one alert. Credentials carry scopes, so the cron job that sends can be forbidden from deleting a channel, and a key can be bound to a single channel. Webhooks push sends, cancels and subscriptions to your endpoint with a signature you verify, instead of you polling us for something you already know. There is also an MCP server, so an assistant can be connected over OAuth — no pasted keys, revocable per client, and narrowed to the scopes you approve on a consent screen you read first.

Draft, schedule, send — and what cancelling cannot undo

Composing and sending are deliberately different permissions, so the person or script that writes an alert can be forbidden from publishing it. A scheduled alert becomes visible at its time without anything having to run at that minute, which means a server that was briefly down delivers late rather than never. Cancelling is honest about its limits: it stops an alert reaching phones that have not fetched it yet and does nothing at all to the phones that already have it. An alert cannot be unsent.

More than one person, without sharing a password

A workspace holds the channels; people are invited into it with a role — owner, admin, editor, analyst or billing. An editor can compose and send; an analyst can read the numbers and nothing else; billing sees invoices and not subscribers. A member can also be restricted to a single channel, which is what a large organisation needs when the communications team and the facilities team should not be able to speak as each other.