productroadmap

What's coming in 2026

January 15, 2026

API Alerts started with push notifications — send an event from your backend, get a notification on your phone. Push was always the first step. The full platform is much more, and 2026 is the year it all comes together: send an event from anywhere, deliver it everywhere.

The goal is simple — your team should get alerts on the tools they already use, with minimal or no code required to set up. Whether that’s a Slack channel, an SMS to the on-call engineer, or a Discord webhook for your community, API Alerts handles the routing so you don’t have to.

Integrations & Event Routing

The biggest change coming in 2026: API Alerts becomes a notification router.

Today, when you send an event, it goes to push notifications. Soon, you’ll be able to route events to any combination of destinations — all from the same single API call you already use.

Destinations we’re building:

  • Slack — post events to channels
  • Discord — webhook-based delivery
  • Email — send to team members or external addresses
  • SMS — text message alerts for critical events
  • WhatsApp — message delivery via WhatsApp Business
  • Webhooks — forward events to any URL

Each destination is configured in your workspace dashboard — no code changes needed. You decide which events go where. A deployment alert might go to Slack and push, while a payment failure goes to SMS and email.

Your existing integration doesn’t change. The same POST /event call works exactly as before. The routing happens on our side.

Event Routing Rules

We’re adding event name matching so you can route different event types to different destinations automatically.

curl -X POST https://api.apialerts.com/event \
  -H "Authorization: Bearer YOUR-API-KEY" \
  -H "Content-Type: application/json" \
  -d '{"event": "payment.failed", "message": "Payment declined for order #1234"}'

A router can match payment.* events and forward them to your Slack finance channel and SMS — while deploy.* events go to Discord and push only.

New SDKs & Tools

We’re expanding language support and adding new ways to send events:

  • PHP — nearing completion
  • Dart / Flutter — for mobile and backend Dart apps
  • Ruby — for Rails and Ruby services
  • Java — standalone JVM support alongside our existing Kotlin SDK
  • Godot — for game developers who want alerts from game servers
  • CLI — send events from your terminal, shell scripts, and CI/CD pipelines without writing code

These ship alongside updated versions of all existing SDKs (C#, Go, JavaScript, Kotlin, Python, Rust, Swift) with support for the new event routing fields.

Teams & Workspace Improvements

Team management launched in February with roles and channel-level access. We’re continuing to build on this:

  • Notification preferences — let team members choose how they receive alerts
  • Audit logs — track who changed what in your workspace

Analytics & Reporting

Understanding your event flow is just as important as sending it. We’re adding:

  • Event volume dashboards — see trends over time
  • Delivery tracking — know which destinations received each event and whether delivery succeeded
  • Workspace usage insights — quota usage, peak hours, most active channels

Beyond the Launch Set

The initial integration destinations are just the start. After the Q2 launch, we’ll be expanding to:

  • Microsoft Teams — for enterprise teams
  • Telegram — community and ops channels
  • PagerDuty — incident management escalation
  • Linear — create issues from events
  • Zapier triggers — use API Alerts events as triggers in Zapier workflows, not just actions

We’re also working on getting listed in the Slack App Directory, Discord marketplace, and other integration directories so your team can discover and connect API Alerts from the tools they already use.

What stays the same

The fire-and-forget pattern. One API call, one line of code, done. The new features are additive — if you’re happy with push notifications today, nothing changes for you. The new routing and destinations are there when you need them.

We’re targeting early Q2 2026 for the integrations and routing platform. Check back here for release announcements.