Sending alerts from an AI assistant
The console calls the same API you would, with the same rules, the same rate limits and the same error envelope. There is no separate integration surface to learn.
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.
A channel asks. The phone decides.
Every channel declares what it would like to be able to do: make a sound, show a banner, override Do Not Disturb, take over the screen, speak the text aloud. Each subscriber grants those one at a time, on their own handset, and can take any of them back later without unsubscribing. Nothing a channel asks for is granted by asking. The loudest thing an unpermitted channel can achieve is an ordinary notification — which still arrives, and still says what you wrote.
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.
Questions, answered plainly
Is there an API?
Yes — the same one the console uses, so anything you can do by hand you can automate. Scoped keys, signed webhooks, and an MCP server if you want an assistant to do it.
Can you guarantee my alert will make a sound?
No, and nobody honestly can. Whether it makes a sound is decided on the handset by what that subscriber granted your channel and by their own settings. What we guarantee is that the alert reaches every subscribed device. Any service promising more is either wrong or is describing a carrier cell broadcast, which is a different thing entirely.
Can I let somebody send without giving them everything?
Yes. Roles separate composing, sending, reading the numbers and seeing invoices, and a member can be restricted to a single channel. The same split exists for API keys, so a script can be allowed to send and forbidden from deleting.
Do subscribers need an account?
No. They install the app, subscribe to a handle, and that is the whole of it. Only the person running the channel signs up for anything.
Say it once. Every subscribed phone gets it.
Free up to 100 subscribers, no card to start, and the handle is yours permanently.
Start a channel