Introducing API Alerts

Building software means constantly needing to know what’s happening in your systems — a new user signed up, a deployment failed, a payment came through. The typical solution is to cobble together a mix of email alerts, Slack bots, and custom webhooks. It works, but it’s fragile and slow to set up.

We built API Alerts to solve this properly.

One API, everywhere

The core idea is simple: you POST an event to our API, and your whole team gets a push notification on their phones. That’s it.

curl -X POST https://api.apialerts.com/event \
  -H "Authorization: Bearer YOUR-API-KEY" \
  -H "Content-Type: application/json" \
  -d '{ "message": "New user signed up", "tags": ["growth"] }'

No configuration files. No webhook endpoints to maintain. No Slack app to install and babysit. Just a single authenticated HTTP request.

Built for teams

Individual developers can use the free tier to monitor their own projects. But API Alerts is designed to scale up to teams — channels let you segment which notifications go to which team members, so your frontend engineers aren’t woken up at 3am by a database alert.

SDKs for every stack

We ship official libraries for JavaScript, Python, Go, Kotlin, Swift, C#, and Rust. They all follow the same “fire and forget” pattern — create a client, call send, move on. No callbacks, no promises to await (unless you want to).

import { ApiAlerts } from 'apialerts-js'

const client = new ApiAlerts(process.env.API_ALERTS_KEY)
await client.send({ message: 'Deploy complete', tags: ['prod'] })

What’s next

Push notifications are just the start. We’re building towards a unified notification broker — the same single API call routes your event to Slack, Discord, SMS, email, or whatever your team actually uses. One integration, all your destinations.

Check out the quickstart guide to send your first notification in under five minutes.