Alert webhooks
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.
Three numbers, and the one we will not print
You get: how many devices could be reached at the moment you sent, how many phones reported opening the alert, and how many acknowledged it. What you do not get is a delivery rate, because there is no per-device delivery record anywhere in this product — that absence is exactly what makes sending to four million people cost the same as sending to four. Reads and acknowledgements are self-reports from handsets that chose to send one, and they are labelled as such rather than dressed up as receipts.
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.
Why is there no delivery rate?
Because there is no per-device delivery record anywhere in the product, and that is a deliberate design decision rather than a gap. A phone’s inbox is a query over sent alerts, which is what makes the cost independent of audience size. We would rather show three numbers we can stand behind than a fourth we invented.
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.
How do people find my channel?
From the handle you give them: on a poster, in an enrolment email, on a QR code, in a footer. Public channels also appear in the app’s discover list. Sealed ones appear nowhere at all, by design.
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